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.
A read channel should be removed from the list of unread channels
A read channel stays under unread channels list
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.
It might be related to new threads support.
We're going to implement it on 4.12.0.
I'm marking as a bug anyway, because I might be wrong and it's something else.
It might be related to new threads support.
We're going to implement it on 4.12.0.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:
Server version: 3.0.10
App version: 4.11
The only way to mark a channel as read is to close and reopen app.
Update:
I notice that when a new message is sent on a channel, it is marked as unread, but it still appears in unread group. If I toggle "Unread on top" option twice the channel correctly disappears from the unread list.
Hi! This issue seems still to be active in 4.12; read messages still stay under Unread header. I can see that the font loses bolding (not very easy to spot with this font), but they don't clean up immediately. Possibly when checking new messages few minutes later they have moved away from the Unread.
@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.
Confirmed working, thanks a lot! :+1:
Good Job. Thank you. :)
Most helpful comment
It might be related to new threads support.
We're going to implement it on 4.12.0.
I'm marking as a bug anyway, because I might be wrong and it's something else.