Stuck notifications: New DMs have stuck notifications

[turt2live]

Steps to reproduce

1. Get invited to a DM
2. Accept & eventually decrypt the person's message
3. Soemtimes, the unread notification badge doesn't go away (but when it does it appears to be local echo)
4. Send a message to reply
5. Sometimes, the badge still doesn't clear.
6. Receive a message from the other party, again
7. Badge goes up to 2 unread messages, despite it only being 1

Outcome

What did you expect?

Not this.

What happened instead?

That :)

This appears to be a multi-week regression, dating back to at least October 24th, 2022. Sending events should be causing the implicit read receipt for my user to be moving up, which means sending messages should clear the notification count. This is not happening, even when sending hidden events in the room.

Restarting the client "resets" the notification counts, if they were cleared by local echo

Operating system

Windows 10 & 11

Application version

Nightly

How did you install the app?

The Internet

Homeserver

t2l.io

Will you send logs?

No

[daniellekirkwood]

Instead of creating a new issue, I also encountered this today morning

[Johennes]

Is this really S-Minor?

Impairs non-critical functionality or suitable workarounds exist

The workaround seems to be opening the DM again to clear the unread badge on every launch. This is a pretty jarring experience not only but especially for new users.

[Johennes]

Also to replicate the little content from #23948: In my case it seemed as if the unread count comes from a cached /sync response on launch.

"unread_notifications": {
  "highlight_count": 0,
  "notification_count": 1