Edited messages in active chats temporarily show as unread despite already being read, with a delayed read status update

[ExtRIELICi]

Using a supported version?

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

Overall summary

If I send a message to someone who is already in our chat, the “read” status appears instantly, as expected, since the person has read it. However, if I edit that same message, the read status does not update in real time as it did when the message was first sent. Instead, it remains marked as unread for a significant number of seconds, even though the person is still in the chat.

This issue can affect multiple messages. For example, if I send four messages and they are all read, but then I edit the third one, it will temporarily appear as unread. But if I send a fifth message right after editing the third message, will that edited third message be marked as viewed.

This bug occurs only on Signal and affects all platforms (confirmed on Desktop and iOS).

Steps to reproduce

1. Open Signal.
2. Open a chat where the other person is present and has not left.
3. Send a message—it will instantly show as read.
4. Edit that message—it will briefly appear as unread, even though it has already been read.
5. (Optional) Send a second message immediately after editing—the edited message and the new message will both be marked as read.

Expected result

When you edit a previously sent message in a chat where the recipient is actively present, the message temporarily appears as unread for a few seconds, even though it has already been read. There is a noticeable delay before the read status updates with edited messages. If you send another message after editing, the edited message is then immediately marked as read.

Actual result

When editing a message in an active chat, the read status should update as quickly as it does for newly sent messages. The edited message should be marked as read almost instantly, without an unnecessary delay.

Screenshots

No response

Signal version

Signal Desktop 7.43.0 ⁨production⁩ (Apple silicon)

Operating system

macOS Sequoia 15.3.1

Version of Signal on your phone

7.47 (625)

Link to debug log

https://debuglogs.org/desktop/7.43.0/89d2cdfb24df3a68104777deefeb512e34bfaf9d701ed5fb85f73e35d0602553.gz

https://debuglogs.org/ios/7.47.0/d413020d1219586d123d90dd16ff17fba925f99733247617535ae20ad4ca1dbc.zip

[adam3941875]

I also noticed this, it has been like this for a long time.

[indutny-signal]

Sorry about this! Happy to take a look! Could you include an example message timestamp along with logs, please? https://support.signal.org/hc/en-us/articles/360054649071-View-Message-Details

[ExtRIELICi]

Hello @indutny-signal,

I am providing you with a newer logs, from Signal Desktop (sender) and iOS (recipient).

The messages were sent by me at March 1, at 15:04 local time.

Timestamps of the edited messages: 1740834266759 & 1740834266941

I was in control of both the PC (Signal Desktop client), and the smartphone (the recipient).

Signal Desktop (sender) log: https://debuglogs.org/desktop/7.44.0/a954b86e52b590ebe7b24332be0c45ef6b19f16e452621725f37854a4a8fd666.gz

iOS Recipient log: https://debuglogs.org/ios/7.48.1/5910bd79a828410da66d99dcf5b27104d69f033ff03c4b2151c2ceb0cd7e433f.zip

[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.

[ExtRIELICi]

Not stale.