Signal stops receiving messages during an active conversation

[bme13]

Guidelines

• [x] I have searched searched open and closed issues for duplicates
• [x] I am submitting a bug report for existing functionality that does not work as intended
• [x] This isn't a feature request or a discussion topic

Bug description

While having a conversation all of a sudden I only see one mark indicating my conversation partner doesn't receive my message. Today I start a conversation with this person while the last conversation was the 25th of January. The first message arrives correctly so it doesn't seem to be an FCM/background issue. Next I receive 2 messages and when sending a new message, this message only get's one mark. These are the timestamps: 11:52, my first message 11:52, 2 reply's 11:54 my next message (containing a photo and text) that does only get one checkmark. (message id: 1738925651377) Called this person and asked to open Signal. Than the message came through. Asked for a debug log, so the attached log is from the receiving device.

Screenshots

No response

Device

Samsung SM-A546B

Android version

14

Signal version

7.31.1

Link to debug log

https://debuglogs.org/android/7.31.1/1d61b2072b4f72bdb1f79a37599c8f119b807b097a50cdf4e773fb36a3f39106

[x64x2]

could be an ISP issue.

[bme13]

In the original description the situation did not resolve automatically but here's a log that I have more frequently with this contact. It's a bit similar in that the original message goes through fast, but the next message takes a much longer time. Here's the timeline: 18:02 original message (id 1739034167965) 18:04 received response, 2 messages 18:06 next message (id 1739034393637) this one takes a few minutes to arrive. Here's the log of the receiving device again. Looking at it I see a couple of onStop/onDestroy messsages. Does that mean the user closes the app?

https://debuglogs.org/android/7.32.2/45e8d028f2781704172b2323ef6a02b31c8b268f1cff10d2837ba09d6a0a5b01

[MR-Bagga]

I'm getting duplicate message exception error do you in which signal or libsignal client version did they solve tis issue?

[bme13]

Here's an other occurrence where I'm having a conversation and some long delays occur in the middle of the on going conversation. This is the receivers log. I've listed the message id's (those are the messages I did send). Please note that on my side I see a single check so the message is delivered to the server. msg id: 1744187629730 Delivery latency: 1 ms, Urgent: true Than a reaction is send. After that I've send msg id: 1744187721450. (send time 10:35:21) And then there's a delay of > 2minutes. Delivery latency: 133925 ms, Urgent: true In between these messages I see: 04-09 10:34:17.041 14331 15643 I ApplicationContext: App is no longer visible
And perhaps as a result: 04-09 10:35:16.421 14331 15643 D IncomingMessageObserver: Background service destroyed. 04-09 10:35:16.773 14331 14336 D InputTransport: Input channel destroyed: 'ClientS', fd=211 04-09 10:35:26.790 14331 14470 D OpenGLRenderer: RenderThread::destroyRenderingContext() 04-09 10:35:27.056 14331 15643 W OkHttpWebSocketConnection: [unauth:242817676] onFailure() 04-09 10:35:27.056 14331 15643 W OkHttpWebSocketConnection: java.net.SocketException: Socket closed I guess this means she switched to a different app or so. According to her she did not swipe the app out of the app list. To me it seems the app get's in the background and it takes a while before the connection is restored. But that's just my laymen's interpretation. https://debuglogs.org/android/7.38.7/c80f642a57a6818bafc58ad42e1676f11daabe630a4110e296e0ef8afe9cc498

[mtang-signal]

Here's an other occurrence where I'm having a conversation and some long delays occur in the middle of the on going conversation. This is the receivers log.

Thanks for the logs! Would you happen to know if the receiver has any battery optimizations turned on? Assuming she's using the A54, she can learn more about it here and here's the general link for notification troubleshooting as well. Only bringing it up because you said that she might've put it in the background when the messages stopped.

[bme13]

The strange thing is that it's never the first message that has a large delay. So sometimes I don't communicate with her for a few weeks and the first message goes through without any delay and than a consecutive message got a delay. To me it seems that if the app is moved to the background it takes a while before it 'restarts'. Anyways I'll ask her about the battery optimization and let you know.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been closed due to inactivity.