element-x-android icon indicating copy to clipboard operation
element-x-android copied to clipboard

Disconcerting "left room" toast

Open spongythecake opened this issue 1 year ago • 2 comments

Steps to reproduce

  1. Where are you starting? What can you see? Frequent left room toast. When I wake the app from being in background activity, there appears a "left room" dialog. The dialog is a long black box that floats over the front of the UI.
  2. What do you click? Nothing. Open the app and it's there. It appears alongside DMs, it appears in room lists, it appears in rooms.

Did you leave any rooms? Yes 24 hours ago, I left a group room using the Element X app. Further, I have engaged in other activities on the app since, like messaging friends.

Toast? It's a modern design word for floating element with a high contrast text. An info dialog could also be used to describe it.

Outcome

What did you expect?

No more constant messages about leaving a room.

Your phone model

Samsung z5

Operating system version

Android 14

Application version and app store

0.4.9

Homeserver

matrix.org

Will you send logs?

Yes

Are you willing to provide a PR?

No

spongythecake avatar Apr 20 '24 07:04 spongythecake

Update, 4 days since the initial event and I am still seeing this message.

spongythecake avatar Apr 24 '24 05:04 spongythecake

I've been trying to reproduce this for some time but I've been unable to. I tried leaving the room from both the room list and the room settings screen and the snackbar/toast is only displayed once. I also tried navigating to other screens, putting the app on background and foreground again, going to background then opening a notification to launch the app and killing/restarting the app.

What's more, the flow that displays these messages is used in a single place, always triggered by a user action, has no replay mechanism to provide the same message to new subscribers (which was my main candidate for a culprit based on the description of this issue), and the subscribers consume and discard the message in a thread-safe way AFAICT, so I couldn't find anything that could cause this.

Does the problem persist even when the app is restarted? Could you send some logs, please?

jmartinesp avatar Apr 25 '24 11:04 jmartinesp

Closing as not reproducible.

bmarty avatar Jun 12 '24 09:06 bmarty