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.

Sign up for GitHub

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

Jump to bottom

Error message: "Delivery Issue: A message from X couldn't be delivered" when no messages were sent #5849

Closed
6 tasks done
achristinek opened this issue Apr 1, 2022 · 26 comments
Closed
6 tasks done

Error message: "Delivery Issue: A message from X couldn't be delivered" when no messages were sent #5849

achristinek opened this issue Apr 1, 2022 · 26 comments
Labels
stale

Comments

@achristinek
Copy link

  • I have searched open and closed issues for duplicates
  • I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Bug Description

I and my colleagues keep getting messages "Delivery Issue: A message from X couldn't be sent." but when we check in with each other, we hadn't sent messages at all.

Steps to Reproduce

I'm sorry, I tried but couldn't reproduce the bug, as it doesn't seem to be connected with any messages I or my colleagues actually send...I hope the screenshots I took will have enough detail to start the investigation; apologies again...

Actual Result: Multiple Delivery Issue messages received on desktop (mac) only, every time I open the app after having shut off my laptop for a while before. I receive 99+ notifications, and several chats show multiple of these messages from different colleagues, when the reality is that no one had messaged at all.

Expected Result: No Delivery Issue message should appear if no one actually messaged.

Screenshots

Chat on Android - no Delivery Issue messages
Chat on mac desktop - 27 Delivery Issue messages
Example conversation on the issue
GroupA on Android screen - no Delivery Issue msg
GroupA on mac desktop version - with Delivery Issue msg
Many chats popping up with Delivery Issue msg when open mac Desktop version
When clicking Learn More under the Delivery Issue message

Platform Info

Macbook Air M1 (MacOS Monterey v. 12.2.1)

Signal Version:
5.37.0
production (M1)

Operating System:
(MacOS Monterey v. 12.2.1)

Linked Device Version:
Android 5.32.14

Link to Debug Log

https://debuglogs.org/desktop/5.37.0/c7c90f95032abb4cba9fabeaedccf7b597c6599385774cb28dd84ffab49ae0e2.gz

In most cases, a log from your other devices is also useful:
Android: https://debuglogs.org/android/5.32.14/1089186844fef183b36ce2133a0a0fd137b41a977cf0471dab303252f1d4de82
@achristinek
Copy link
Author

Hm I see the file titles didn't make it through. Please msg me if you need more intel on the comparisons, but essentially the dark background is from Android, the light background is from desktop mac.

@maticahacic
Copy link

I have same issues on Arch Linux and Android phone.

@indutny-signal
Copy link
Contributor

@maticahacic could you include your debug logs from both phone and Desktop, please?

@maticahacic
Copy link

Absolutely. My bad.

Linux: https://debuglogs.org/desktop/5.37.0/469ed4c15e02b3c692c6a95336cd8119934bfb0d562b682e193129cc5eef55bb.gz

Android: https://debuglogs.org/android/5.34.5/dd1becdb124e6d8ead199307b54b2f4faa6ccb154ad2976b298e776a80e7deda

@stale
Copy link

stale bot commented Jul 6, 2022

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 stale bot added the stale label Jul 6, 2022
@kmellerup
Copy link

kmellerup commented Jul 11, 2022 •
edited
Loading

I had the same problem in Signal Desktop (Kubuntu 20.04 Linux) today when I started a computer that has been off for more than two weeks. Maybe around 50 of those "A message to X couldn't be delivered"

@scottnonnenberg-signal
Copy link
Contributor

@kmellerup It is expected that you'll see some problems after having desktop offline for so long. But 50 errors is surprising. How many messages would you say that you send and receive per day?

@stale stale bot removed the stale label Jul 11, 2022
@achristinek
Copy link
Author

achristinek commented Jul 11, 2022 via email

@scottnonnenberg-signal
Copy link
Contributor

@achristinek Believe me, I have lots of Signal Desktops linked. In fact, I often have five Signal Desktops linked to my account. I think the difference is that I don't leave any of them unopened for two weeks.

@achristinek
Copy link
Author

achristinek commented Jul 11, 2022 via email

@scottnonnenberg-signal
Copy link
Contributor

@achristinek Well, next time it happens please provide a debug log from both the receiver and sender - we want to track these errors down!

@kmellerup
Copy link

@scottnonnenberg-signal Ok, understandable. Usually I do not have it off for that long and it didn't really bother me but since I found this issue and it seem to be the same I wanted to let you know.
How many messages... hmm, never really counted and it probably differ from day to day but between 10 and 100 maybe? Not sure if you mean overall Signal or just that particular chat group that the errors were in.

I took out a debuglog yesterday. Not sure if that would help.
https://file.io/17TmKYfzQzgb

@scottnonnenberg-signal
Copy link
Contributor

scottnonnenberg-signal commented Jul 12, 2022 •
edited
Loading

@kmellerup All of your errors are of type LibSignalError: missing sender key state for distribution ID [REDACTED] which means that you missed an earlier message from that device with the information necessary to decrypt that group message.

You got a lot of errors:

Errors by Sender - 7 total

| Key   | Value |
| ----- | ----- |
| f2e.1 | 107   |
| aed.1 | 51    |
| f0c.2 | 47    |
| aed.2 | 26    |
| ce4.1 | 7     |
| 123.1 | 6     |
| ea3.1 | 2     |

You can find these folks by searching with a special keyword for these users. For example, !uuidEndsWith:f2e to search for the first user you got a lot of errors from in that list.

The errors are actually expected because they are about two weeks old - the first message that resulted in an error had a timestamp of 2022-06-27T08:38:37.179Z, which is right about two weeks ago. You had Desktop offline for long enough that you started losing messages (anything over two weeks old), namely the messages that had the key material required for decrypting that message.

Finally, I'll say that these kinds of things do happen, and they often don't result in Delivery Issue items in the timeline - because Signal clients will request message retries in this case. 169 of your 246 errors were successfully retried, leaving 77 messages as Delivery Issue in your conversations. For those messages, the sending devices perhaps weren't online when they needed to be for the retry.

@kmellerup
Copy link

kmellerup commented Jul 13, 2022 •
edited
Loading

Ok, I understand. Desktop turned off more than two weeks and I think a new user might have joined the group chat where the errors occurred during that time, and everything has been as it should be in my android phone. Thank you for the nice summary, Scott!

@achristinek
Copy link
Author

achristinek commented Jul 13, 2022 via email

@erzwo31
Copy link

erzwo31 commented Sep 20, 2022

I do experience the exact same behaviour as the author. Sometimes in 1to1, sometimes in group chats.
OS: Pop!_OS 22.04
Kernel: 5.19.0
Signal: 5.59.0
Debug from Desktop

Android 12:
Debug from Android

@indutny-signal
Copy link
Contributor

@erzwo sorry about that! Did you have your Desktop app turned off for more than two weeks?

@achristinek
Copy link
Author

achristinek commented Sep 21, 2022 via email

@scottnonnenberg-signal
Copy link
Contributor

@achristinek The reason it had problems when you had it installed on multiple computers was because you copied data between the two devices but didn't unlink and re-link. So, the two installations conflicted with each other. If you ever copy data between computers in the future, unlink that device on your phone then re-link, and things should be in good shape.

@achristinek
Copy link
Author

achristinek commented Sep 22, 2022 via email

@indutny-signal
Copy link
Contributor

@achristinek on your phone there is a menu where all linked devices are displayed. I believe on Android you can swipe on a certain device and it will offer you to unlink it. On iOS you probably need to tap "Edit" in the top-right in order to be able to do the same. Once unlinked - this particular Desktop will ask you to re-link and will show the steps to do so.

Hope this helps!

@achristinek
Copy link
Author

achristinek commented Sep 28, 2022 via email

@DieterLudwig
Copy link

@achristinek The reason it had problems when you had it installed on multiple computers was because you copied data between the two devices but didn't unlink and re-link. So, the two installations conflicted with each other. If you ever copy data between computers in the future, unlink that device on your phone then re-link, and things should be in good shape.

YOU MADE MY DAY!
Thank you

May you could add a more detailed Explanation when click on "Learn more" of "A Message from xxxx couldn't be delivered"

@stale
Copy link

stale bot commented Jan 19, 2023

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 stale bot added the stale label Jan 19, 2023
@stale
Copy link

stale bot commented Jan 27, 2023

This issue has been closed due to inactivity.

@stale stale bot closed this as completed Jan 27, 2023
@AkechiShiro
Copy link

Just encountered the issue today.

@bbernhard bbernhard mentioned this issue Apr 6, 2024
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale
Milestone
No milestone
Development

No branches or pull requests
8 participants
@kmellerup @DieterLudwig @AkechiShiro @erzwo31 @maticahacic @scottnonnenberg-signal @indutny-signal @achristinek