Skip to content
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

Messages are not received by some contacts #8934

Closed
4 tasks done
Yky opened this issue Jul 20, 2019 · 7 comments
Closed
4 tasks done

Messages are not received by some contacts #8934

Yky opened this issue Jul 20, 2019 · 7 comments

Comments

@Yky
Copy link

Yky commented Jul 20, 2019


Bug description

Messages are not received by some contacts. Only one check mark is shown after sending the message. The recipient has internet connection.

Steps to reproduce

  • Open Signal
  • Send message to single user

Actual result: Only one check mark appears. Recipient does not receive the message.

Expected result: Messages are received if the recipient has an internet connection.

Device info

Sending device:
Device: Pixel 2
Android version: 9
Signal version: 4.43.8

@greyson-signal
Copy link
Contributor

I can't do much with this report, unfortunately. It could be any number of things, and without having logs from the sender and receiver, I can't debug further. However, it's probably safe to assume that this is probably a case of delayed FCM messages, which is a known problem we're working on. Thanks!

@Yky
Copy link
Author

Yky commented Jul 23, 2019

@greyson-signal
The sender runs without FCM, the receivers are Huawei phones with FCM.

I can only provider sender logs at the moment.

@Yky
Copy link
Author

Yky commented Jul 24, 2019

Update: The messages are received when the receiver opens the Signal app.

@greyson-signal
Copy link
Contributor

Yep, that sounds like a known issue. You can have your chat partner go to this page, which describes various phone-specific ways to omit us from battery optimizations and whatnot (which could prevent us receiving notifications).

https://support.signal.org/hc/en-us/articles/360007318711-Troubleshooting-Notifications

However, even after following those steps, there are still situations where notifications could be delayed, and I'm actively thinking about solutions.

@alcoolfire
Copy link

@greyson-signal: Would you kindly provide a link to that known issue you're referring to? All I can find is you closing issues #8934, #8841, and #8579 without solutions. If there is no open bug report, then please reopen this one or create a new one so that affected users can follow along. This problem is very badly damaging the usability of Signal.

I am aware of 3 different phones that have used Signal successfully for a long time that now fail to get notifications once they've been sleeping for a while. Although one is a Samsung Galaxy, the others are a Nexus 5 and a Moto G3, so I think its safe to say this is not a Samsung problem. No configuration changes have been made to any of these phones in the transition from functional notifications to unreliable notifications.

As an anecdote for the Nexus 5, I do not have a data plan for it, so Signal only works with Wi-Fi. For years I've been accustomed to hearing notification chimes as a I drove into my driveway and Wi-Fi came into range. Now I get nothing until I manually wake the phone (usually plugging it into the charger).

@Yky
Copy link
Author

Yky commented Aug 4, 2019

Yep, that sounds like a known issue. You can have your chat partner go to this page, which describes various phone-specific ways to omit us from battery optimizations and whatnot (which could prevent us receiving notifications).

https://support.signal.org/hc/en-us/articles/360007318711-Troubleshooting-Notifications

However, even after following those steps, there are still situations where notifications could be delayed, and I'm actively thinking about solutions.

I think a lot of users will not be able to locate that article page, as the app does not give any hint on what to do if messages are not being delivered. I hope this is only temporary solution.

@nicobatty
Copy link

Hi, I'm having the exact same problem on my Galaxy S10e, sometimes I only receive messages when I actively open the app.

Here is my log: https://debuglogs.org/353a3874578cf2c86525bb3ee927a57d18906bb83d8baa845ce337fabeef5c1f

I received 5 messages between 18:20 and 18:27. I opened the app at 18:42 with the 5 notifications.

Happened again a few minutes later, received first message 18:45, second message at 18:58 and opened the app at 19:07 with the 2 notifications.

There seems to be this java.io.EOFException before I received both the 18:20 and 18:45 first messages. Maybe that can be the cause of the issue? There is basically 0 log between 18:20-18:42 and 18:58-19:07 even though there were 7 messages I should have received on these ranges.

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

No branches or pull requests

4 participants