Multiple read marker shown and looped messages

[worldowner]

After I upgraded Element yesterday to 1.4.20 weird things started to happen. You can see them on attached screenshot.

As you can see on the screenshot read marker is displayed multiple times in room which has only 2 members. When I select the marker it shows list of "seen by" all form the same user. They all show the same time.

I have pruge set to 1 day on my homeserver. Element loops messages from last 24 hours (effect is visible on the screenshot). Clearing cache doesn't solve the issue however number of read markers changes. Also when I scroll up the number of read markers increases. This happens on all rooms that have messages. Rooms that have no messages inside also seem to be in some kind of loop.

My client is: Element/1.4.20 (Linux; U; Android 12; SM-F926B Build/SP1A.210812.01; Flavour GooglePlay; MatrixAndroidSdk2 1.4.20)
The problem didn't occur on any previous Element client. It is also not present on self-hosted element-web.

[akoyaxd]

I could reproduce this Issue on Element 1.4.16, 1.4.18 and 1.4.20; all gplay.

I only hat this issue on federated dm's, which were started after the upgrade to 1.61.0. Downgrading both homeservers of the two participants to 1.60.0 seems to have fixed it.

[akoyaxd]

#6312

[worldowner]

I only hat this issue on federated dm's

This is not the case for me. I have a room that has 2 members both on the same homeserver and there is the same problem.

[ouchadam]

this may have been fixed in 1.4.22 with #5528

[worldowner]

I upgraded Element Android to 1.4.25. Empty rooms (by empty I mean those that have been purged by synapse) are still in some kind of loop. Rooms with messages are fixed.

[532910]

It's still here with 1.5.11.

[svenb1234]

It's new for us and appeared with the last update. However there are always only two markers from the same person in a 1:1 chat. One marker is after the latest message, the other below the one before the last.

[opusforlife2]

Same ^. Until 1.5.10 everything was fine. On 1.5.11, I've started seeing the double read receipts. One occurred in a single DM, and one in a group DM.

I'm sure the bug occurred after I 'replied' to a message in the group DM (not the read receipt duplicating person's).

Based on this, and the fact that I 'replied' to the single DM person as well before I started seeing the bug, I think this could have something to do with threads. But I've never turned Threads on in Labs. And it isn't on by default.

[SpiritCroc]

I think the duplicate read markers starting from 1.5.11 is a new bug and comes from the threaded messages implementation: it shows both the read markers for threadId null and "main". A solution could be only showing one of them, but I find concerning that they usually differ by at least one message.

[opusforlife2]

I can second that. The difference is nearly always of 1 message.

Edit: It's happening in every chat where I've sent and received messages after updating to 1.5.11.

[anaqreon]

I confirm this dual, non overlapping duplicate read receipt behavior on version 1.5.11 [40105110] (F-40bfffae). It affects rooms created before and after 1.5.11.