Skip to content

Messages not sent using WiFi/Mobile Network #8382

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
4 tasks done
Edu4rdSHL opened this issue Nov 18, 2018 · 1 comment
Closed
4 tasks done

Messages not sent using WiFi/Mobile Network #8382

Edu4rdSHL opened this issue Nov 18, 2018 · 1 comment

Comments

@Edu4rdSHL
Copy link

Edu4rdSHL commented Nov 18, 2018


Probably related with #8365, if it's the same, feel free to close it and sorry.

Bug description

Messages stop being sent since the latest Signal releases in random times, messages are seen in the "Sending" state. It's happening non only for me, it's happening also to my friends that are using signal since months ago.

Steps to reproduce

  • I can not describe "how to reproduce" because it happens in random times without specific conditions and not for all users at the same time. When i taked the screenshot I was sending/receiving messages from anothers user.

Actual result: Messages keep in the "sending" state anyways if network are available.
Expected result: Messages are sent.

Screenshots

20181117_193056

Device info

Device: Samsung SM-G610M
Android version: 8.1.0
Signal version: 4.30.6

Link to debug log

https://debuglogs.org/944ef395438a506e2dd788bb1c38ef479c10111456caa1961a7c765b19baab2d

@greyson-signal
Copy link
Contributor

This actually looks like a dupe of #8370.

2018-11-17 18:12:12.758 GMT-05:00 I Job: [fb3ead61-9646-41b9-ab13-c2c3e2266bef] PushTextSendJob :: Retrying due to unmet requirements. (Time since submission: 898502 ms, Run attempt: 4, isStopped: false)

It looks like the first message took a while to send for whatever reason (log doesn't go back far enough to say why, maybe poor network), and then your screen locked. At this point, messages will fail to send and increase the time between retries to the point where when the app is open, the time between retries was getting pretty long (minutes). To add to that, messages sent in the same conversation need to wait for the previous message to send, so the whole convo gets kinda stuck.

There's a fix for this in the next beta release that should release early this coming week (I didn't want to put it in this latest release due to the risk of the change). In the short term, you can consider switching to a manual screen lock (basically remove the timeout and lock the screen via the notification after your messages send). And you can get these latest messages to send by leaving the screen lock off until they go through.

Sorry for any frustration -- this should be fixed soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants