-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Error message: "Delivery Issue: A message from X couldn't be delivered" when no messages were sent #5849
Comments
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. |
I have same issues on Arch Linux and Android phone. |
@maticahacic could you include your debug logs from both phone and Desktop, please? |
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. |
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" |
@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? |
Hi all,
Wanted to say that I'd get sometimes 90+ if the group chat I was in was
particularly chatty (though it didn't necessarily correspond with the # of
messages), and I'd have desktop on daily. One thing I tried that seems to
have "fixed" the bug is that I uninstalled the desktop version from my work
laptop. Previously, I'd had Signal on two laptops + my phone. After
downsizing to one laptop and one phone, I stopped getting those messages.
Perhaps try testing by having a single Signal account across a couple
phones and a couple desktops - I think you'll probably end up seeing this
bug.
Hope that helps!
…On Mon, 11 Jul 2022 at 18:02, Scott Nonnenberg ***@***.***> wrote:
@kmellerup <https://github.com/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?
—
Reply to this email directly, view it on GitHub
<#5849 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYQGRVREOPNVA4XJHRN6WR3VTRHUBANCNFSM5SHYMGPQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@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. |
Neither did I, but the issue kept happening.
…On Mon, 11 Jul 2022, 18:24 Scott Nonnenberg, ***@***.***> wrote:
@achristinek <https://github.com/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.
—
Reply to this email directly, view it on GitHub
<#5849 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYQGRVVJH3B47XIU453NLGLVTRKFXANCNFSM5SHYMGPQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@achristinek Well, next time it happens please provide a debug log from both the receiver and sender - we want to track these errors down! |
@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. I took out a debuglog yesterday. Not sure if that would help. |
@kmellerup All of your errors are of type You got a lot of errors:
You can find these folks by searching with a special keyword for these users. For example, The errors are actually expected because they are about two weeks old - the first message that resulted in an error had a timestamp of 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. |
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! |
Hi Scott,
Ofc shall do!
…On Mon, 11 Jul 2022, 19:25 Scott Nonnenberg, ***@***.***> wrote:
@achristinek <https://github.com/achristinek> Well, next time it happens
please provide a debug log from both the receiver and sender - we want to
track these errors down!
—
Reply to this email directly, view it on GitHub
<#5849 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYQGRVRPAIRQRVXPMH4FBJTVTRRLDANCNFSM5SHYMGPQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I do experience the exact same behaviour as the author. Sometimes in 1to1, sometimes in group chats. Android 12: |
@erzwo sorry about that! Did you have your Desktop app turned off for more than two weeks? |
Hi there, I wrote the original issue!
Don't know if this will help for you, but the issue stopped after I
uninstalled Signal Desktop from my second laptop. I had had Signal desktop
on my work laptop AND my personal laptop, as well as the Signal app on my
personal phone. Now that I only have Signal desktop on one laptop, no more
issues...though it is a faff to not be able to have it on multiple devices.
…On Tue, 20 Sep 2022, 18:40 Fedor Indutny, ***@***.***> wrote:
@erzwo <https://github.com/erzwo> sorry about that! Did you have your
Desktop app turned off for more than two weeks?
—
Reply to this email directly, view it on GitHub
<#5849 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYQGRVXBDXUC6LE5VSRRU5TV7I4NDANCNFSM5SHYMGPQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@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. |
What do you mean by unlink and relink? Thanks!
…On Wed, 21 Sep 2022, 20:45 Scott Nonnenberg, ***@***.***> wrote:
@achristinek <https://github.com/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.
—
Reply to this email directly, view it on GitHub
<#5849 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYQGRVWJ4MSCIKIHD54QACDV7OTZLANCNFSM5SHYMGPQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@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! |
Thanks, tried it - I'll let you know if it acts up again.
…On Thu, 22 Sept 2022 at 12:21, Fedor Indutny ***@***.***> wrote:
@achristinek <https://github.com/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!
—
Reply to this email directly, view it on GitHub
<#5849 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYQGRVUEIW7A7A3XOO52S6DV7SBQRANCNFSM5SHYMGPQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
YOU MADE MY DAY! May you could add a more detailed Explanation when click on "Learn more" of "A Message from xxxx couldn't be delivered" |
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. |
This issue has been closed due to inactivity. |
Just encountered the issue today. |
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
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
The text was updated successfully, but these errors were encountered: