You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Open Signal.
Open a chat where the other person is present and has not left.
Send a message—it will instantly show as read.
Edit that message—it will briefly appear as unread, even though it has already been read.
(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)
Using a supported version?
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
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
The text was updated successfully, but these errors were encountered: