Cannot persistently clear unread messages in rooms containing threads

[novocaine]

Steps to reproduce

Load my account in our test server. See this

Click on all of the rooms in the room list to clear unread

Reload the page and the unreads are back

Outcome

What did you expect?

For the unread markers and badges to not return after they were cleared

What happened instead?

They came back

Operating system

OS X

Browser information

Chrome

URL for webapp

develop.element.io

Application version

Element version: ba55473-react-c19aa957b655-js-74d24f38f742 Olm version: 3.2.8

Homeserver

threads-dev.lab.element.dev

Will you send logs?

No

[germain-gg]

I'm not sure whether this is related to threads or not.
This is happening in a DM where 0 threads have been created.

Have not figured out the root of the issue yet

[novocaine]

This is no longer happening in group rooms on the test server, but it is still happening with the DM

[kittykat]

I semi-regularly have red and grey notifications appearing in Delight with no obvious messages/reactions/threads/etc to account for them

[novocaine]

I can't repro this any longer

[novocaine]

Seeing this again in "Threads Internal". It's marked permanently in bold and nothing I can do clears it

[novocaine]

I managed to clear this by adding a reaction not in a thread

[novocaine]

I can't clear the unread marker in Threads P0 Delivery today at all.

[t3chguy]

Blocking on threads notifications msc work

element-hq/element-meta#196

[davepacheco]

I'm seeing a very similar behavior:

1. Every time I load Element, many rooms show unread messages.
2. I navigate to every room with unread messages and they're marked read.
3. I refresh Element -- now they all show "unread" again.

I'm using Element version: 1.11.8 (Olm version: 3.2.12) in Firefox 105.0.1 on Mac OS 11.6.8. This has been going on with my Element session for about a week, since we recently updated our Matrix server for the recent security update.

I just checked to see what happens in my mobile (iPhone) client. I noticed that some rooms show unread messages that should not have (I had seen all the notifications). I went through and read them. Now those rooms don't show as unread in either the browser or the mobile client. But there remain other rooms (I think they're all currently DMs) that show unread messages in Element in the browser, but not on my mobile client. That remains true even if I refresh the browser and restart the mobile client. And it remains true even if I navigate to them on the mobile client.

Maybe relevant: I saw similar behavior with the Element MacOS app several weeks ago. I gave up using the app (without debugging it further) because this problem was such a pain. At that time, this was not affecting Element in the browser. But now it is.

Is there any other data I can provide to help resolve this?

[germain-gg]

This issue will be resolved when clients all implements matrix-org/matrix-spec-proposals#3773

Element Web is tentatively close, and both Android and iOS will fast follow, matrix-org/matrix-js-sdk#2726

The problem is "resolved" and pending implementations

[t3chguy]

@thiemol 1.11.31 is 50 days old and 3 versions of fixes have happened since then. Please consider our time when reporting issues with old versions where active fixes have been made since.

[wielinde]

Hi, we use Element in our relatively big team on many operating systems (Linux, MacOS, Android, iPhone,...). Thank you all for that great application!

Our clients are as up-to-date as you can get it in a diverse team (the majority is on the latest Element version, however, possibly some e.g. on mobile phones could be outdated).

We encounter the problem of having wrong "unreads" all over the place (different users, OS, versions,...). Also the inability to successfully mark a room as "read", even when restarting client and/or deleting the cache multiple times.

Unfortunately the pain is so big in the team that people started openly express their anger during meetings. The main pain points are:

• Not being able to mark some rooms as read, again and again
• Thus, not trusting the "unread" badges anymore and consequently missing out important messages

If we miss anything crucial information/tip on how to resolve the mentioned issues please point us to a solution. We were not able to figure it out from the messages above.

Also, if we are the only team having that issue, I'd also appreciate the feedback as we then probably need to shift our debugging focus on our Matrix server (Synapse version 1.90.0.). However, it does not look like that. Other Matrix clients do not seem to have the same problems.

We are team of software developers and could provide you with deeper and more detailed information if you need it. I am personally available for a debugging session.

Thank you!

[ayushin]

why is this issue closed, the problem is clearly there

[samuelcostae]

Having the same issue, usually with threads that are months old

[Tropaion]

Also having this issue, very very annoying.