Signal-desktop: "Original message not found" for quoted message which is still present

Created on 12 Dec 2020  路  1Comment  路  Source: signalapp/Signal-Desktop

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

Bug Description

I have a GV2 group chat with 10 members, disappearing messages set to 1 week.
This issue occurs only at linked desktop client. On iOS mobile client there is no problem these very messages.

The issue: on desktop client if I click on quoted message in message-3, it throws an "Original message not found" popup, meanwhile the quoted message (message-2) is present, it is NOT missing, it is above 2 steps away from message-3. The order of messages are OK.

Important: at the time of these messages were sent, this desktop client was offline. It synced them all when I turned on this desktop computer.

Message-1:

  • Sent ID: 1607782534645
  • Sender: xxx759
  • has 2 reaction emojis

Message-2:

  • reply to message-1
  • Sent ID: 1607783741719
  • Sender: xxx164
  • Click on the quoted message: OK, jumps to to message-1

Message-3:

  • reply to message-2
  • Sent ID: 1607784938624
  • Sender: xxx759
  • Click on the quoted message: "Original message not found"

Message-4:

  • reply to message-3
  • Sent ID: 1607788116551
  • Sender: xxx164
  • Click on the quoted message: OK, jumps to to message-3

Steps to Reproduce

It's stochastic, it happened one time.

Actual Result:
I click on quoted message in message-3, "Original message not found" popup is shown.

Expected Result:
I click on quoted message in message-3, it jumps to message-2.

Screenshots

none

Platform Info

Signal Version:

  • Signal Desktop 1.39.2 (Mac OSX)
  • Signal iOS 5.0.1.1

Operating System:
Mac OSX Big Sur

Linked Device Version:
iOS 14.2

Link to Debug Log

Signal Desktop 1.39.2 (Mac OSX):
https://debuglogs.org/e64c0c38e173a1c69c06d4998a30a954ab0167fff5c78ae98ce9d5f50a59c646

Signal iOS 5.0.1.1:
https://debuglogs.org/638b28e2b5d38130251e9099444c9a18bf6cb585ab4e43e9bec83773c53cb8dc.zip

Bug

Most helpful comment

We believe we've fixed this problem in the latest version, so I'm going to close. Let me know if that's wrong and we can reopen.

>All comments

We believe we've fixed this problem in the latest version, so I'm going to close. Let me know if that's wrong and we can reopen.

Was this page helpful?
0 / 5 - 0 ratings