element-hq / element-hq/element-android
Sending a "quick reply" in a notification leads to clinging "unread" messages in the room
- Dominant language
- Kotlin
- Stars
- 3.7k
- Forks
- 917
- PR merge metrics
- No merged PRs in 30d
Description
Each time I use the "quick reply" action from within a RiotX Android notification, the following happens:
- my answer is sent successfully,
- the corresponding room in RiotX shows an "unread message" (probably the message I answered to − maybe already at this point this is a bug),
- if I open the room in RiotX, the "unread message" counter remains, as if opening (and scrolling through) the history in the said room does not manage to make the new message count as read − sometimes I kept unread counters on rooms for whole days,
- only if I open the same room in Riot web, the message is finally registered as read, and the "unread message" counter disappears from the room in RiotX as well.
In other words, it seems there is a bug in tagging messages as read/unread when the quick reply action is used?
Contributor guide
Assessment
This issue has not been assessed yet.