Signal-desktop: "Reading" reactions does not sync between desktop and mobile

[max-rosenfors]

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

---

Bug Description

Reactions produce notifications when they are received, reading (or rather, witnessing/seeing (?)) these notifications on Signal-Desktop does not remove the notifications on a synced corresponding mobile device.

Steps to Reproduce

1. Have a mobile client synced with a desktop client.
2. Have an active chat.
3. Receive a reaction to a message that you sent.
4. "Read" the notification of a received reaction to that message on your desktop client.
5. Unlock and check the mobile device, there should be a push-notification present that is not cleared by reading the reaction on desktop.

Actual Result:

The desktop client does not sync reading reactions to your mobile device.

Expected Result:

The desktop client syncs reading reactions to your mobile device.

This behavior is correspondent with the current functionality regarding notifications of actual messages. In that case the notifications and read/unread behavior syncs correctly.

Platform Info

Desktop version: v1.38.2
Mobile version: v4.78.5 (Android)

Operating System:

Desktop version: Ubuntu 20.04
Mobile version: Android OxygenOS v10.0.1

[rphair]

I also have this problem more generally: of the message read status itself not being synced.

Signal on Android, until about a week ago, always cleared the new message notification after that same message was read on Signal Desktop. Now that no longer happens: reading the message isn't enough to dismiss the Android notification... it has to be manually marked as read on the mobile device.

I'm not submitting this as a Signal Android bug (yet) since there appears nothing wrong with how the mobile app itself works.

Desktop (Ubuntu 18.04) version: v1.39.2
Mobile (Android LineageOS 16.0) version: 4.79.3 (debug log)

[rphair]

The previous comment can be disregarded: I was reading my own debug log which inventoried all the mobile app permissions, then decided to check my XPrivacyLUA settings. There is a setting there for "Read notifications" which I could see Signal was being denied by default: I opened up that permission and then things worked as before.

So whatever changed recently in the mobile or desktop app, they now require this permission (granted by default from unmodified Android) to work together properly.

[netopolit]

Anyone know how to fix this on iPhone? I am using Signal desktop for Mac and the iPhone app. Read status from the desktop client is not syncing to mobile.

[kaimast]

Same issue for me on Ubuntu 20.10 with the flatpak version of Signal.

[EvanHahn-Signal]

We don't currently sync whether you've read a reaction. As far as I know, none of the clients (Android, iOS, or Desktop) do this. But this is on our radar—thanks for reporting.

No need to comment further.

[tobiscode]

I also have this problem more generally: of the message read status itself not being synced.

Signal on Android, until about a week ago, always cleared the new message notification after that same message was read on Signal Desktop. Now that no longer happens: reading the message isn't enough to dismiss the Android notification... it has to be manually marked as read on the mobile device.

The previous comment can be disregarded: I was reading my own debug log which inventoried all the mobile app permissions, then decided to check my XPrivacyLUA settings. There is a setting there for "Read notifications" which I could see Signal was being denied by default: I opened up that permission and then things worked as before.

So whatever changed recently in the mobile or desktop app, they now require this permission (granted by default from unmodified Android) to work together properly.

I have the exact same problem - if I read a message on Desktop, the notifications do not disappear anymore on the phone, even after waiting several minutes. This wasn't always the case, and I see you originally opened the issue in December, so my problems might have very well started around that time, too.

However, I do use an unmodified Android (just Netguard, but here Signal has all the rights), so I can't solve the problem by checking/modifying privacy settings as far as I can tell. Any other ideas? If I send a debug log through the app, is there anything I need to do to connect it to this issue?

Edit: Since I guess technically this issue is about read reactions and not read messages (even though it came up), I guess I'll go ahead and create a new issue.

[bob46859]

Seems to be the same issue as #9501

[EvanHahn-Signal]

This is on our radar. Hopefully we'll be able to get to it soon.