Room stuck as unread despite all messages/threads marked as read (to my knowledge)

[turt2live]

Steps to reproduce

Unclear

Outcome

What did you expect?

No stuck notifications.

What happened instead?

See rageshake. The threads list icon indicated that there weren't any unread threads, and I've read all messages in the main timeline to my knowledge. Still have a stuck notification.

Operating system

Windows 11

Application version

Element Nightly version: 0.0.1-nightly.2023053001 Olm version: 3.2.14

How did you install the app?

The Internet

Homeserver

t2l.io

Will you send logs?

Yes

[turt2live]

Sending a message to the main timeline fixed this case for me.

[weeman1337]

Added to the stuck notifications epic for investigation.

[turt2live]

It appears as though this is caused by the most recent message in the main timeline being a thread root (and thus threads under it). The read receipt appears to be confused.

[audunmb]

I have this as well. I left click and mark the room as read, still shows as unread. I open all threads and place the marker in the reply field below, to make sure that the thread is marked as read. Still it shows as unread.

[Standard8]

I also have this on a room and I've just sent logs for it.

Interestingly if I use the Element mobile app for the room, the room there shows as unread, but if I try and go into the threads view, then I get "RealmList does not accept null values", which is an error that can't be cleared.

[Standard8]

One possible step to repeat:

• Have a room that you're subscribed to that receives a new message and thread.
• View the room but not the thread.
• Mark the room as read.
• View the thread.
• Close the thread view.

At this stage, you're now stuck in the unread state.

I've just sent debug logs for this.

[samim23]

I get this sort of bug all the time on https://app.element.io/ and its highly annoying. Unread badges will reappear multiple times often, despite manually saying "i have read this". Sometimes it will even just say hundreds of old messages are unread, especially when heavily using threads. It happens daily, to the point where matrix/element feels like a broken UX.

[oliverguenther]

This happens to me as well on a daily basis using Element on Mac and Linux (Version 1.11.35 both cases)

[t3chguy]

Believed to be fixed by matrix-org/matrix-js-sdk#3600