An incoming message isn't synced to the Desktop

[KommX]

• I have searched open and closed issues for duplicates

---

Bug description

A single incoming message is not synced to my Desktop application. This does not happen for any other incoming messages. So I can't reproduce unfortunately.

Steps to reproduce

1. I open Signal on Android.
2. I see the message.
3. I open Signal on my Desktop.

Actual result:

I can't see the incoming message after my "Ende 2013, Anfang 2014" and before my "Ich glaube, nicht so lange. Muss ich noch mal nachgucken."

Expected result:

I can see all messages on all devices.

Screenshots

Platform info

Signal version:

1.16.3

Operating System:

Windows 10

Linked device version:

4.29.0

Debug Logs:
Desktop;
https://debuglogs.org/056149bac5d9f0c91dd93653af29d469c8cd38d724eb35e9886c6cad482fb55c

Android:
https://debuglogs.org/812aca555d943d9431337657ae38aaf29a76110be958d3ba0b5d7b111c35e90b

[scottnonnenberg-signal]

Please go into the message that didn't show up on Desktop and grab its 'sent id' by going into message details and then long-pressing on 'Sent: ' line. That should copy its 'sent id' to the clipboard. That will help us cross-reference the missing message in both logs.

[KommX]

The send id should be:
1539678319859

[KommX]

Can I (or should I) remove the "Need Information" label?

[scottnonnenberg-signal]

Is it perhaps shown lower in the conversation? In the log, the application was closed before it was processed properly the first time. But perhaps it was processed successfully the second time, and because it was processed later it showed up later?

[KommX]

No, it isn't. The message is still "gone".
Maybe this is related to issue #2876?

[tuukka]

I had the same happen here when I started Signal desktop on Ubuntu 18.04:
https://debuglogs.org/3832487a5b61d39419dab21a0dd05c4fc342c2d6e92390f1336fa1b4e9abd67f

The "sent id" of the message that is missing on desktop is 1543776068798.

[Flupkees]

This happens to me all the time. Can I provide any information that would help solve this bug?

[scottnonnenberg-signal]

@Flupkees As with all reported bugs, the first thing we look for is a debug log, and it needs to be submitted quickly because it only captures three days of activity. The next thing is a detailed report of the behavior you saw and the specific messages which are missing - you can go to your mobile app, find the missing message, go to the more info/details screen for that message, then long-press on the 'Sent' header to copy its 'sent id' which allows us to find that message in the Desktop Log. Thanks!

[bentolor]

@scottnonnenberg I have had the same issue right now the second time within 2 days in the same conversation: Received message shows up on Android client but not on Desktop app or vice versa. Even after replying the lost message stays lost and does not appear.

RECEIVED Message visible on Android Client Missing on Desktop: Right now

• Missing received: Appears on Android Client only. Permanently missing on Desktop client
• ID as seen on Android client: 1546552705882. Retrieved via long-press on Received in Android App.
  ** My successfull, subsequent reply from Desktop ("blind"): 1546552873712.
  ** The previous, successfull message before the missing one: rec: 1546547203102 sent: 1546552765722 (no idea: is the sent id the read notification?)

SENT Message via Desktop missing on Android Client: Yesterday

• Message missing: Sent via Deskto. Not appearing on Android App:
• IDs as seen on Desktop App: recevied: 1546440409291 sent: 1546440446180

Both cases are present within the Desktop client log files (see link). I do not know how to retrieve the Android log file, though this would only be relevant to the second message.

Please see the full logs here: https://gist.github.com/bentolor/59b6401040d5d2377ad4e472d73d1fc1

[scottnonnenberg-signal]

@bentolor The 'sent id' is the one which is shared between all devices, and generated on the sending side. So that's the one we want to use when analyzing logs. Of the ids you provided, only one message can be found in your linked log - your reply with id 1546552873712. I cannot find the rest of the IDs in the log!

[bentolor]

@scottnonnenberg I asked my communication partner to pass me the phone so I was able to verify the correct "Send IDs" from all Sender Devices. I linked them for your convenience. I was also able to spot one of the problems.

Case 1: RECEIVED Message visible on Android Client Missing on Desktop: Right now

It turns out: The issue is that this message is displayed completely out of order and is visible on Desktop client very faaaaar back!

The send message ID of the message Thu 22:58 (Do. 22:58) entry is 1546552704126.
The history continues chronologically after that Entry. Roughly more than 40 entries until 22:58 !

Actually it should be displayed here: between those two messages I sent:

1. „Nein. Wir spielen ein Ratespiel“ is 1546547203102
2. „Ich geh jetzt schlafen. Hoffe es geht dir gut :-*“ is 1546552704126 and is only visually missing and appears way above
3. „Alles gut. Gerade daheim angekommen“ is 1546552873712

Case 2: SENT Message via Desktop missing on Android Client

Correct Sent ID is: 1546440409291. I mixed send and recv ID. To avoid any doubts, here the details screen from my desktop client:

Message „Schrader hat mir zwei Packungen der gleichen Charge geschickt." as seen on desktop client:

Message missing on MY android client

Due to the lack of a search function I was not able to verify, that this message might be visible somewhere else in the history. I did not find it on scrolling through the history.

Unfortunately it is also missing on the receiver device!

Nota bene: Those audio recordings were something where I tried to demonstrate the audio messaging service to someone else. But the did not appear… at first… After 3-4 tries suddendly all of them appeared. I deleted them on my device (that's why they are missing in my Android screenshot and probably thats the thing behind those empty messages?. Nevertheless: This happened on 2018-12-29 while my lost message was sent on 2019-01-02.

Was I able to persuasively convey the issue?

[scottnonnenberg-signal]

Thanks for the details. It's not about persuasion, it's about having enough information to try to address the source of the problem!

[bentolor]

Addendum: My communication partner just confirmed, that she did receive/see the missing 1546440409291. Probably only via Android popup notification. So it appears to be mostly a presentation issue with delayed/out-of-order received messages.

As far as I can see from the screenshots of the original bug report, my case #2 seems to match that one: He sent a message from desktop which is marked as delivered but does not appear (at all/in the right place) on the Android client.

[kyraha]

https://debuglogs.org/b9aa629ddce9becf8bd99f61d81c090605219780da95bf903a5036ffa4c1491d
Sent ID: 1549042128687

Replicate:
After a break enough for some backlog to build up open the desktop. While it is loading the backlog of messages send a new message to someone. The message will be missing in the desktop app.

Note:
It happens not only to your own sent messages but to other's messages too originated while the desktop app is loading.

[scottnonnenberg-signal]

@kyraha I think you'll find that, in that loading scenario, the message is indeed in the conversation, it's just higher up in the conversation than you expect. Any message processed after you sent that message will be sorted below it.

[kyraha]

@scottnonnenberg-signal

@kyraha I think you'll find that, in that loading scenario, the message is indeed in the conversation, it's just higher up in the conversation than you expect. Any message processed after you sent that message will be sorted below it.

That's right, thanks! Confirmed and reproducible. The messages I or anybody else just sent while the desktop app was loading are inserted into the old conversation randomly, or rather by luck. Basically the messages in the conversation window are sorted by the "Received" timestamp instead of the "Sent" one, I see. Interesting. Time is indeed a fascinating problem in distributed systems.

[Dyras]

@scottnonnenberg-signal This just happened for me.

https://debuglogs.org/1d0797ed31f8eb7d9520a6852af87314d8ac14db5bbf6a8ef02a9f0f333332c0
Message ID: 1550078133317
Sent the message to a friend and for some reason it's higher up than it should be.

Is there a separate issue for that btw?

[scottnonnenberg-signal]

@Dyras There are bugs talking just about message ordering. So yes. :0)

[stale]

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]

This issue has been closed due to inactivity.