Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notifications unread status not being sync #2235

Closed
taoeffect opened this issue Jul 19, 2024 · 2 comments · Fixed by #2248
Closed

Notifications unread status not being sync #2235

taoeffect opened this issue Jul 19, 2024 · 2 comments · Fixed by #2248

Comments

@taoeffect
Copy link
Member

taoeffect commented Jul 19, 2024

Problem

On Desktop on the GIG group, all notifications are read, but on my phone on the PWA, these are not only unread, but clicking "Mark as read" doesn't do anything:

Screenshot_20240719-154053

Screenshot_20240719-154051

EDIT: what's odd is that this works on the testing website...

EDIT2: OK, after @Silver-IT joined the group, suddenly the notifications looked like this:

tmp-1721429497316

In other words:

  • The two notifications that I had clicked "Mark as read" on PWA that wouldn't mark themselves as read, suddenly became read.
  • The new notification came in as unread
  • And this time I was was able to click "Mark as read" and it did sync

Solution

Fix.

@dotmacro
Copy link
Member

dotmacro commented Jul 20, 2024

I just encountered this issue again on desktop. Using two different devices:

  1. (already signed in and using app on device1)
  2. Sign in on device2. The notifications that were marked as read before I signed in on device2 remained marked as read on both.
  3. Mark new notification as read on device2. (Same new notification is not automatically marked as read on device1.)
  4. Mark as read does not work on device1.
  5. Refreshing page does not help, nor hard refresh. Restarting browser does not help. Restarting device does not help.
  6. Log out device1 and log back in.
  7. Notification now automatically marked as read.

@Silver-IT
Copy link
Member

Having tested several times on my side, I can not encounter this issue. 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants