The problem is still happening on 9.11.1.
Here is an example sequence for me:
- I am online as normal; all channels are fully read
- I go offline (close laptop etc)
- At some point while offline, someone creates a new group message or private channel that has me in it
- I come back online, and lots of unread channels are shown in the sidebar (but the new group/private channel is not shown as unread, and maybe is in a collapsed group)
- I read all the unread channels - now the sidebar shows nothing unread
- …but there is a number in the red circle in the title bar, indicating that there are still unread messages
This happens regularly enough that I recognise it. I know that refresh will cause the unread channels to appear in the sidebar. Recently I also discovered that simply collapsing/expanding a channel group in the sidebar is also enough to make the unread channel appear in the sidebar. Maybe that helps to diagnose where it is going wrong?
I don’t understand what you mean about the sidebar settings - not sure what any changes to the settings would avoid this bug?
Because I am a user who likes to mark everything as read, I get the fallback indication from the unread messages indicator in the title bar; users who leave lots of channels marked unread by default do not get that fallback and they are much more concerned.
This is still the most common complaint about mattermost at my workplace. Surely there is some information that could be captured next time we see that we are in the broken state (sidebar showing nothing unread, but the unread indicator at the top showing that there are unread messages)? I could get screenshots but I am not sure they add anything beyond the description. Is there any datastructure in the webapp that we could dump? I believe that in every case in which I have seen this, it has been on a new channel created while I was offline - a new group, a new private channel, or maybe a new conversation with another user with whom I have not chatted before (which internally does mean a new direct channel has been created as I understand it). This doesn’t mean it is reproducible every time but I think this must help to narrow it down? Seems that there is some request to the server to list channels that is being missed, or maybe that query is failing when I open up my laptop (maybe during a messy period of getting networking reconnected) and is not retried? Or maybe the new channel is known and it’s a display bug with the collapsed channel groups (given that simply collapsing a different channel group causes it to appear)?
I would really appreciate it if the developers could look at this since it has been a troubling bug for several years now. Happy to participate and help out with gathering information on our side if it helps.