search

element-hq / riot-android

A glossy Matrix collaboration client for Android
Apache License 2.0
1.4k stars 394 forks source link

Outgoing messages sometimes get duplicated and stuck to the bottom of the history #3511

Closed theastrallyforged closed 4 years ago

theastrallyforged commented 4 years ago

Occasionally, when I send a message, it'll go through, but a copy of it will stick to the bottom of the conversation history. This copy is timestamped with the time I tried to send the message. Long-pressing it produces an overlay with my name and the message (like other messages), but no options. New messages appear above it. It also causes the timestamp of the conversation and the unread-messages indicator in the conversation list to stick as well (reflecting the timestamp of the stuck copy and no new messages, rather than updating as new messages are received). The clear sending queue command is available in the hamburger menu when a stuck message copy is present, but does not affect it. Leaving and rejoining the conversation doesn't affect it either.

The first time this happened, there was a progress indicator next to my name in the long-press UI, and using the clear sending queue command did work to remove it. I believe Element has been updated at least once after that; it's subsequently happened to me twice more (once in the same conversation and once in another).

Distinct from #2081, which is about established events that actually have timestamps in the future.

theastrallyforged commented 4 years ago

Whoops, wrong repo, sorry. I'm using Element Android, where this is issue 1119