-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Rocket.chat mobile application does not mark channels as read #2519
Comments
It might be related to new threads support. I'm marking as a bug anyway, because I might be wrong and it's something else. |
I think you rigth. I see this with new threads on 3.6.3 server |
We have the Same Problem. |
Same problem here:
The only way to mark a channel as read is to close and reopen app. |
Update: |
Hi! This issue seems still to be active in 4.12; read messages still stay under |
@Gummikavalier Can you post a gif/video? |
@diegolmello Yes, I also confirm that behaviour. Tested on 4.12.0.21382 version. If you look on the screen, the top channel has been read, but still stays in the "Unread" section. Even though it is not bold anymore. This is a bug and the issue should be reopened. Or a new issue opened. |
@diegolmello Yes, exactly how @zdumitru has it in his pic. The message does get marked as read, but it just doesn't disappear from under the Unread. |
* Fix parent title on thread header breaking lines * Fix #2519 * Fix thread badge not being updated
Confirmed working, thanks a lot! 👍 |
Good Job. Thank you. :) |
Description:
Recently we've had a constant issue that on both iOS and Android mobile app does not mark any new unread channels as read after visiting them in the mobile client. The situation gets fixed either by closing the app from the history, or clearing its local cache.
Environment Information:
Steps to reproduce:
Expected behavior:
A read channel should be removed from the list of unread channels
Actual behavior:
A read channel stays under unread channels list
Additional context:
We have noticed this issue with two separate RC server instances / workspaces. Both of them have push notifications disabled, so it might be related to late changes to notification handling on the mobile client.
Other possible triggering factor could be changes in the app to cache more data locally on the client end.
The text was updated successfully, but these errors were encountered: