Signal-desktop: After joining V2 group "Error handling incoming message" messages are received from group members on Desktop

[robertpicciotti]

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

---

Bug Description

I joined a V2 group. I have an iPhone and a linked Desktop client (the beta) on the most recent MacOS (Catalina). Any message received from that conversation (I think including read receipts and such) results in a "Error handling incoming message" response in a one on one conversation with whoever sent the message. However, the actual group conversation does successfully give a notification that looks correct and the group itself seems to behave correctly.

Steps to Reproduce

1. Join a V2 group
2. Begin receiving messages

Actual Result: See one on one conversations with members of the group report errors. The group itself behaves correctly.

Expected Result: The group itself behaves correctly without erroneous one on one conversations.

Screenshots

Platform Info

Signal Version: 3.18.0.4

Operating System: iOS, MacOS

Linked Device Version: v1.36.2-beta.2

Link to Debug Log

https://debuglogs.org/2fbd7e2d484e1bfbcdde53a7e0debf27413b6a18646e733b83c5a34ff087b200

[josh-signal]

@robertpicciotti are you able to send messages to the group?

[arikb]

I'm getting this as well, but not from within the group - outside of the group as individual messages. The group chat is clean of these messages, but I get new chats with individual group members that are full of these same errors.

v1.36.2-beta.2

Edited to add:

Debug log:

https://debuglogs.org/8f33b3ece32b3ceb6a4676a4e28f639273a4f9d3f9130b307073156ac0086696

Just to clarify, I had the desktop client open when I was joined to the new group. I wasn't near the computer though. When I came back I saw my computer shut down. I restarted it (2020-09-25T10:32:44.471Z is the timestamp when I restarted) and then saw the aforementioned messages.

Edited again:

https://debuglogs.org/736136339b4ab094585bee9a846c1fffc07fe296eb4b104af2874cd05c1d0f64

This new log is after more of that happened:

[robertpicciotti]

@robertpicciotti are you able to send messages to the group?

I am able to send messages to the group, both from desktop and my phone.

[josh-signal]

@arikb @robertpicciotti we believe to have identified an issue and fixed it. It's on the latest beta: 1.36.3-beta.1

Sending a message to the group should help unblock ya'll in the meantime.

[arikb]

It's on the latest beta: 1.36.3-beta.1

I just installed the new beta; I'll wait for someone new to join the group and see if it has been resolved.

[arikb]

Okay looks like it was resolved for me. I see the messages in order and no private chats full of errors.

Just one thing though - the acceptance message of a new user shows the new user was invited by "Unknown User"

https://debuglogs.org/6be870b2f8f26cbc778b9ea2af3c4dc283dd3411b9cba25b294cf99fe24eebae

[scottnonnenberg-signal]

@arikb What do you see when you go to the group members screen from the top-right menu?

[arikb]

You can see Matt in the middle

Edit: pixelated numbers and names that look like they're real

[scottnonnenberg-signal]

@arikb Just to confirm, it was Rainer Zufull who invited Matt?

[rainerzufall]

Yes, I invited Matt.

[severus-tux]

I got the same errors on signal desktop. Initially I used v1.36.3 on Ubuntu 20.4. I got _"Error handling incoming messages "_ on from three different people (not in the group. Outside the group). On my android, I am using 4.72.2. These error messages _didn't_ appear on my android.
Here is the debug log from my desktop v.1.36.3: https://debuglogs.org/4143abb3a45da4a999f2a105e32ad025bfaa27adf6ddcc3594675eb0fc6d32fd

Then, I opened signal-desktop-beta (v1.36.3-beta2). Same thing happened. I got new error messages from one more person.

Here is the debug log from signal-desktop-beta (v1.36.3-beta2) : https://debuglogs.org/e5744f24eec616e2f19a0151247cb0c8e9f97dfe05e136e3a8e916333220db7d

[scottnonnenberg-signal]

@severus-tux That error came from split contact merging - what can you say about how you (and this Desktop instance) first found out about that user? Somehow we got two contacts for them.

WARN  2020-09-27T14:01:31.481Z ensureContactIds: Found a split contact - UUID [REDACTED]3c3 and E164 +[REDACTED]313. Merging.
...
ERROR 2020-09-27T14:01:40.040Z queueEnvelope error handling envelope +[REDACTED]313.3 1601215297886

At the very least, going forward you shouldn't get errors from them. Either a message to them or a reset session should fix things.

[m-leclercq]

EDIT : I fixed it by unpairing then re-pairing my computer. But as I did it, someone else in the group chat caught a variant of the bug (where they can see my messages in the group convo and in our private convo but they keep receiving "Error handling incoming message") in our private convo. Unapiring and re-pairing fixed the issue for them aswell.

I just started having this issue on Kubuntu 20.04 with Signal v1.36.3.
My linked phone device is on Signal 4.71.5 for Android.

What exactly happened was:

-A week or so ago I booted my computer and installed Signal. Synchronizing the desktop version with my phone took a long time and I had to shut down the computer before it was over.
-Today I boot my computer, open Signal, leave it some time to synchronize with my phone. It takes a while, but all my group conversations and most of my individual conversations synchronize properly.
-Then I start receiving an endless flood of "Error handling incoming message" in one of my private conversations with a person that is a member of one of my group convos.
-Clicking "More Info" on those messages gives me an Error : 'Over 5000 messages into the future! New:7880, Existing: 1' (see screenshot)

-The very weird thing that's happening and that I haven't seen in the other messages pertaining to this issue, is that those private messages sometimes have reactions from people that are in our common group convo.
-I cannot see the messages that this person sends on the group conversation, even when they 'quote' one of my messages. I also cannot see the reactions that they send (be it on my messages or other people's)

What I've tried to do to resolve this issue:

-Send a message to the person
-Tell the person to send me a message on the private convo
-Restart Signal
-Restart the computer
-Re-import phone contacts
-Reinstall the desktop app

What fixed the issue:

-Unpairing my desktop device then re-pairing it.

Additional details:

-The person with the bugged convo changed their profile name a few days ago.
-I have three desktop devices linked with my Signal account : one on Windows and one on Kubuntu 19.10 (which both work perfectly) and one on Kubuntu 20.04. All of my devices are on the same timezone.

Here is my desktop app debug log:
https://debuglogs.org/c4be17151e02eb338c72f62325ed00b936928911bb68056373eb505da365ab3f

[scottnonnenberg-signal]

@m-leclercq Thanks for all those details - can you talk about what parts of that story are covered by that log you've provided?

[m-leclercq]

The log was produced right before uninstalling the app.

[scottnonnenberg-signal]

@m-leclercq Your shows us that there is an error, but the problem is that it doesn't show us the transition into the error. We really need a log that shows you receiving messages successfully from a contact, and then errors starting. Then we could try to attach it to some sort of event.

Today we don't really know why these errors start. There are two clues we have from your report. Shutting desktop down in the middle of downloading a large queue, and being offline for a while. There does seem to be a pattern on the second one, where occasional usage causes more frequent errors, based on other reports we've seen.

One thing you can do to help us out on that is to capture regular logs, so that when you go for a while without using desktop, you'll have logs from the before and the after.

[m-leclercq]

The thing is, there was no transition and it happened right as I opened Signal.

I'll be sure to produce a few logs where Signal works as intended. Should I send them here or just submit them in-app?

I was going to send you one right now but I'm having another issue that will need its own post because I don't think I've seen it reported before. It does seem somewhat related to this one though? Anyways I'm going to finish writing the report and then you'll see what I mean.