With one particular conversation partner, both of us being on the non-playstore version (all other contacts use the playstore version), messages will often not be delivered and be stuck on one checkmark.
Pretty much the same as described in #6246 by @EvanK - my conversation partner and i are on Lineageos 14.1 as well.
Additional info:
-It also happens that my conv. partner has single checkmarks too, but i did receive the messages. This was the case when i made the screenshot. On the other phone, sent messages had one single checkmark, my messages were missing.
-It may happen for only one of us, i.e. unidirectional communication, other side is stuck with single checkmarks
-Force quitting & restarting, resetting network etc. does not help. Not even a reboot.
After upgrading the app, the error was gone for about 24h and then started again.
I am opening another ticket after reading #7598.
Actual result: At any point in a conversation, messages will stop to obtain a second checkmark for an indefinite amount of time.
Expected result: Messages should be delivered as usual.

Device: Sony Xperia Z5 Compact (suzuran)
Android version: 7.1.2
Signal version: 4.21.6
Debug log of the other end: https://debuglogs.org/f1e601c46416d3600cdedcbac49e93e5a6dcd62c14a369fc4c5e2d8a205e8735
By the way: the same thing happens when sending from signal desktop.
I will try to single out what makes it happen/stop ..
I can confirm that bug with two Samsung phones (S7 with Android 8.0 and S5 mini with Android 6.0.1) and with the playstore version of Signal Messenger. This only happens from time to time, and I have no idea how to reproduce it. Other times it just works. But I have to admit, that I haven鈥檛 experienced that bug since about 10 days.
The bug here: The message arrives at one phone, but the other phone shows the message only with one check mark.
I think (as far as I remember) the bug could be related to the bug #7733 of not being able to start/receive calls and only getting a message of a missed call, while the caller continues hearing the submarine echo sound.
Could it be connected to #7638 ?
Could it be connected to #7638 ?
I'm not sure. At first glance, the logs seem to indicate that the network connection is ok. For some reason though receipts are not received (or processed) and there are also suspicious messages about delayed notifications, which are then canceled.
As a first step, I'd suggest upgrading to the latest stable version, as this one is more than a month old and the logs seem to contain failure messages of the autoupdate mechanism. I recently had similar problems after staying with an old version of Signal, even though it was patched to take care of #7638.
Im seeing this issue as well. Im on the beta via play store (4.25.5) - contact is on regular version from play store (4.24.8).
It kind looks like the recipient device sleeps a bit too much - my initial thought was that it was due to some battery optimizer function, but turning optimize off hasnt changed anything.
Any suggestions, news, ideas?
I have a contact that does not receive notifications of messages that I send as well.
This is the debug log of my Signal Desktop (from where I sent the messages):
https://debuglogs.org/6d2f70749a11276477fe8765647a1ea926014efdf5bccbe6b37dbfea0d036466
This is the debug log of the contact who does not receive notifications (it looks like Signal does not wake up from the background, or is not running in the background). The debug log is taken after activating Signal and receiving the messages:
https://debuglogs.org/eb4a29c1253f2be64a3fcf15b3550682812a534ec214c45f913195c299872ee0
I also noted, that in Signal Desktop, one message was not marked as received by my contact while is was received:

Maybe it's because of battery optimisation in android if the user doesn't use signal often.
Many other apps check this and display a information about this with a link into the settings, so that the user can disable the optimisation.