Signal-desktop: Signal desktop says messages were delivered but receiving client never received any messages

[fat-racoon]

• [ ] I have searched open and closed issues for duplicates
  

---

Bug Description

I have problems sending and recieving messages from my contacts lately. The app notification says that the message is send and has arrived but it never actually shows up at the receiving end. The problem does not occur generally but only occasionally and it has happened, that my messages are being recieved, but i don't reveive messages from the same contact and vice versa.

Steps to Reproduce

1. step one
2. step two
3. step three

Actual Result:

Expected Result:

Screenshots

Platform Info

Signal Version:

Operating System:

Linked Device Version:

Link to Debug Log

[kenpowers-signal]

Hi, @fat-racoon. Can you provide us with debug logs from the Signal Desktop device you are sending messages from as well as debug logs from the clients which are supposed to be receiving the messages? Screenshots and other information requested in the issue template would also be very helpful!

[jerkey]

i'm experiencing this as well. I confirmed with multiple recipients (both who have worked at EFF and are also Desktop users) that they did not receive messages with a single checkmark, but some subsequent messages do go through. Strangely, a message I sent which was not received (and shows one checkmark) reports as being "Received" at the same instant it was sent (see picture)

[saemy]

This issue seems related signalapp/Signal-Android#9356.

[santa-klaus]

I posted debug logs for Android in https://github.com/signalapp/Signal-Android/issues/9356, which could very likely be the same problem. Unsure how useful they are though.
For some restarting the session seems to help. Since it seems to also affect desktop users it seems like this is not an issue with the energy saving settings on phones.

[dewanee]

I can confirm the issue with 1.29.3 and that it disappers with 1.29.6.
As displayed in @jerkey screenshot the message sent through signal-desktop seems to be accepted by the server (1 tick) but not delivered (second tick missing).
This silent failure is quite annoying as it gives the impression the recipient is offline and will receive the message eventually.

[d3xter]

For me, sending messages through the Linux-App doesn't work at all (only a single Tick), but sending a message via Android works fine.

The messages and ticks are synced between Linux and Android, but they never get delivered.

And BTW, I'm running 1.29.6

[deutrino]

This is happening to me on Signal Desktop 1.29.6 and Signal Android 4.53.7.5922. I see double-check "delivered" status on all messages but the recipient sees nothing. It started a few days ago.

[sbraz]

For me, sending messages through the Linux-App doesn't work at all (only a single Tick), but sending a message via Android works fine.

The messages and ticks are synced between Linux and Android, but they never get delivered.

I have the exact same issue and I'm running 1.29.6 too. The problem started less than 24 hours ago, it worked fine until 6PM CET yesterday.

I've tried deleting all my Signal Desktop config and I can link the device again but contacts are not synced and sending messages now fails:

{"name":"log","hostname":"desktop-pc","pid":341941,"level":30,"time":"2020-01-23T13:31:08.608Z","msg":"Send pre-checks took 4 milliseconds","v":0}
{"name":"log","hostname":"desktop-pc","pid":341941,"level":30,"time":"2020-01-23T13:31:08.610Z","msg":"Sending message to conversation +[REDACTED]040 with timestamp 1579786268610","v":0}
{"name":"log","hostname":"desktop-pc","pid":341941,"level":30,"time":"2020-01-23T13:31:08.679Z","msg":"SQL channel job 47 (saveMessage) succeeded in 26ms","v":0}
{"name":"log","hostname":"desktop-pc","pid":341941,"level":50,"time":"2020-01-23T13:31:08.719Z","msg":"Message.saveErrors: Failed to retrieve new device keys for number +[REDACTED]040 Error: OutgoingMessage.doSendMessage: accessKey was provided, but senderCertificate was not\n    at OutgoingMessage.doSendMessage (file://[REDACTED]/app.asar/js/libtextsecure.js:39956:9)\n    at file://[REDACTED]/app.asar/js/libtextsecure.js:39775:21\n    at async OutgoingMessage.sendToNumber (file://[REDACTED]/app.asar/js/libtextsecure.js:40159:7)","v":0}
{"name":"log","hostname":"desktop-pc","pid":341941,"level":30,"time":"2020-01-23T13:31:08.743Z","msg":"SQL channel job 48 (saveMessage) succeeded in 20ms","v":0}
{"name":"log","hostname":"desktop-pc","pid":341941,"level":30,"time":"2020-01-23T13:31:08.744Z","msg":"SQL channel job 49 (getOlderMessagesByConversation) succeeded in 21ms","v":0}
{"name":"log","hostname":"desktop-pc","pid":341941,"level":30,"time":"2020-01-23T13:31:09.397Z","msg":"SQL channel job 51 (updateConversations) succeeded in 21ms","v":0}

[quaqo]

Came here looking if someone encountered the same issue.

This was happening to me as of 2 hours ago also: messages sent by Desktop shown as 1 tick and synced on Android, but not received on the other end.

I tried resetting the secure session without luck.

I finally realised I was on 1.29.3, and I just updated to 1.29.6 and reset the sessions again (no deleting of config or else). Now is working. I'll update if it will stop again.

So 1.29.6 seem to have fixed it for me, for the past 5 minutes.

[quaqo]

Could #3845 be related?

[bengan]

Same problem here. The problem started this monday for me. At the start some of the messages weren't delivered. Later in this week all of the messages showed up as delivered but none were.

Signal Android 4.53.7
Signal-desktop 1.29.3

Signal-desktop upgraded now to 1.29.6

[d3xter]

So I've decoupled the Desktop-App and recoupled, but now I can't send messages anymore.
Seems like getting the profile/key of my contact fails with a 503

debug.log

[scottnonnenberg-signal]

For those of you running into this, please first update to the latest Signal Desktop, v1.29.6, released about a week ago. Then, once you've started that release up, if you are still having send problems, please provide a full debug log (not a snippet of it, as some of have provided up-thread).

[sbraz]

I just noticed that I was not running v1.29.6 as I initially thought. Actually updating to 1.29.6 fixed the problem for me.

Maybe someone else has the same problem so here's what happened: I had installed signal-desktop-bin from AUR and it was recently added to Arch Linux under the name signal-desktop. This prevented the package from updating and I made a mistake while checking the package version with pacman (I should have looked at the version from the app instead).

I'll remove myself from the issue, sorry for the bother.

[dderder]

Same issue after iOS app update from yesterday. Could no longer send from signal Desktop (v1.29.1) on OSX nor from the iPhone. Messages stayed hanging with one checkmark.
The comment from scottnonnenberg-signal saved me. I downloaded v1.29.6 from the website and it all started working again. Thanks!

[jerkey]

i'm experiencing this as well. I confirmed with multiple recipients (both who have worked at EFF and are also Desktop users) that they did not receive messages with a single checkmark, but some subsequent messages do go through. Strangely, a message I sent which was not received (and shows one checkmark) reports as being "Received" at the same instant it was sent (see picture)

I was experiencing this (I posted in issue 3909) and after updating Signal Desktop to 1.29.6 it stopped happening. I am pretty sure the problem was only happening while my laptop was open (and Signal Desktop was running)

It seems to me that the appropriate fix for these kinds of issues (besides developers avoiding the kind of bug that was introduced and caused this) would be a banner message in the Desktop app that reminds/requires people to update when necessary. As a linux user, updates only happen when I manually do them (and manually restart signal-desktop)

[hellboy1975]

Just to add my 2c to this. For me:

• Messages are sent and received just fine from my Android and Windows Signal apps
• Messages sent from my Linux app are visible on all my devices, however don't get sent to the intended recipient
• Recipient confirms they can only see messages sent by me from Android/Windows

[scottnonnenberg-signal]

@hellboy1975 Your bug report isn't very useful to us without a version number. Any build which isn't newer than v1.29.6 is very likely to have problems like you describe. If you are on the latest, please provide your debug log (View -> Debug Log).

[jerkey]

Seeing as this is apparently a Desktop issue (which was fixed by updating Signal Desktop) I think the lesson to be learned is that Desktop needs more robust checking for whether it's outdated enough to suggest (with a banner) or require (with a refusal to proceed) rather than accidentally causing serious problems like unsent messages. A worse story comes from my friend whose 2nd laptop had not been open for a month, and when he opened it and Desktop started syncing, it caused so much chaos: "I fired up the other laptop and it connected, then started spewing hundreds of messages with encryption errors back to my other clients somehow. Then it screwed up my phone and was making it hot and draining the battery, even after reboot. I had to wipe all the messages on the phone."
I'll ask him to post here, but you get the idea: Desktop needs to be more careful when it's outdated.

[hellboy1975]

@hellboy1975 Your bug report isn't very useful to us without a version number. Any build which isn't newer than v1.29.6 is very likely to have problems like you describe. If you are on the latest, please provide your debug log (View -> Debug Log).

Thanks @scottnonnenberg-signal - it does look like the desktop is out of date: running v1.29.0. I thought I'd updated, but perhaps not.

[toxpal]

Using 1.29.3 on Linux and have exactly the same problem (started this week, I think).

I receive messages without any problems, but I can't sent any messages with Signal Desktop. No errors or warnings, but after I send message, Signal desktop only displays it was sent (but never delivers message to the recipient).

If I use Signal for Android, messages are sent and delivered perfectly, problem exists with desktop client only.

Also I think it's worth mentioning that after I send message from Signal Desktop, I instantly see this sent message in my Signal for Android (which means message at least reaches Signal server) but message is never delivered.

[d3xter]

Alright, so something went wrong with Gnome Software + Flathub. It showed that Verison 1.29.6 was installed, but inside the debug-log it said "starting version 1.29.4".

After reinstalling the App, the Version 1.29.6 is running and sending/receiving messages works again.

[toxpal]

The latest version for Arch users is 1.29.3 at the moment, hopefully 1.29.6 will be available soon, so I can test it too.

[quaqo]

The latest version for Arch users is 1.29.3 at the moment, hopefully 1.29.6 will be available soon, so I can test it too.

That's not accurate.

Last version in community is 1.29.6 and in community-testing is 1.30.0.

Check that your community mirror is up to date, if not change it, and then run:

pacman -Syy signal-desktop

[toxpal]

Sorry, my bad. It looks I was using signal-desktop-bin package for some reason (which was always receiving updates too), so I removed it and installed signal-desktop. You are right, it's version 1.29.6 and messages are delivered again. Thank you for pointing out.

[ruphy]

Same here. With the same exact account, Signal on Android delivers the message, Signal 1.29.4 Desktop doesn't, updating to Signal 1.30 (with a simple apt dist-upgrade) fixes the message delivery. I discovered this after a couple of days of being able to message my contacts from my phone only.

[sarahscheffler]

Same issue here, a single checkmark would display, the message also showed up on my phone, but it was never received. I'm running Fedora 29, using luminoso's COPR repository since the official Signal release only supports debian-based distros. :'(

Debug log here, set to expire after 1 day: https:// send (dot) firefox (dot) com/download/d507fb4e5e4d21eb/#JpcQ_bBOtmOMYXjwELPshA

One note, since someone mentioned GNOME -- I'm not running GNOME, I'm running Sway.

I'm not sure what version I was running before -- it was probably VERY old -- but installing version 1.30.0 seems to have fixed it, at least for now.

[santa-klaus]

For me running Signal Desktop 1.29.4 prevented even Signal on my Android from delivering messages - sometimes even when the computer was suspended.
Please note that 1.29.4 is the current version in the ubuntu repos, so updating means reinstalling from a different source for users who have used those sources so far.

[denver-s]

Version 1.30 fixed the issue for me.

[muki]

https://github.com/signalapp/Signal-Desktop/issues/3926 is a possible duplicate of this.

[numin0us]

Updating to version 1.30 fixed this for me as well.