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

Highlight notifications stuck #3263

Closed
Tracked by #3363
PureTryOut opened this issue Feb 18, 2017 · 4 comments · Fixed by matrix-org/matrix-react-sdk#1147
Closed
Tracked by #3363

Highlight notifications stuck #3263

PureTryOut opened this issue Feb 18, 2017 · 4 comments · Fixed by matrix-org/matrix-react-sdk#1147

Comments

@PureTryOut
Copy link

Seemingly randomly, notifications sometimes get 'stuck'. Opening the room and marking all messages as read doesn't clear them out

@ara4n
Copy link
Member

ara4n commented Feb 18, 2017

To investigate this i suspect we need a rageshake - please ping here once you've submitted one from User Settings on riot web

@ara4n
Copy link
Member

ara4n commented Mar 5, 2017

I have one of these at the moment. It looks like the server just gave me an unread count for that room in /sync, which then got stored in indexeddb, and has never been overridden (until presumably the next message is read in the room). This looks distinctly like a serverside issue.

@ara4n ara4n removed the ambiguous label Mar 5, 2017
@PureTryOut
Copy link
Author

Good that you can reproduce it, as I didn't get a proper rageshake yet... The option for that should really be added to the desktop client. Anyways as long as Synapse is updated when the fix for this lands, it should be gone?

@ara4n
Copy link
Member

ara4n commented Jun 26, 2017

should be fixed by matrix-org/matrix-react-sdk@#1147

@ara4n ara4n closed this as completed Jun 26, 2017
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.

2 participants