element-x-android
element-x-android copied to clipboard
element-hq
Notifications persist after you read a room from another client
Steps to reproduce
- Receive a message in a room
- Open that message from another Matrix client like Element Web
Outcome
What did you expect?
The message notification should disappear when I read the room. This is what Element Web/Desktop and Android do. The notification does not disappear even if you open Element X Android. You have to go to the specific room.
What happened instead?
The notification stays there.
Mentioned here too: https://github.com/vector-im/element-x-android/issues/1923
Your phone model
No response
Operating system version
No response
Application version and app store
Today's nightly
Homeserver
No response
Will you send logs?
No
Are you willing to provide a PR?
No
I also run into this issue. It is even the case if you have the client open.
Also, the notification updates in the room list (green dot disappears if I open the room in another client) but not in the android notification center. Pressing on the room in the room list on the android client removes the notification however.
I'm also experiencing this issue, it seems to be identical behaviour as https://github.com/element-hq/element-android/issues/4862
Given the behaviour is the same, do the team recognise that this is a bug? Or is the app meant to work this way?
I still experience this with matrix.org homeserver on 0.7.4 (fdroid) with ntfy and a friend of mine also experiences the same issue with a mostly same setup but self-hosts synapse.
We were just talking to another about this issue via matrix and could immediately repro.
I don't think I've ever not seen this happen with Element X. Could we upgrade this to "always"?
What I'd be interested to know is whether anyone is not able to repro this. This is so obvious that anyone working on Element X developers must have noticed it immediately, so perhaps there's a significant difference in configuration between their setups and ours.
Is anyone able to repro with firebase messaging/the Google play version for instance?
I'm also experiencing this issue, it seems to be identical behaviour as element-hq/element-android#4862
Given the behaviour is the same, do the team recognise that this is a bug? Or is the app meant to work this way?
FWIW, I don't see this behavior (via firebase) on Element (1.6.28) but only on Element X (0.7.6) and it's really ~~distracting~~ annoying. So no, this shouldn't be intended behavior but rather a bug in Element X.
100% a bug. Very annoying to see a notification on your phone, think it's a new message, then realize it's an old one you already replied to on your laptop. Would be a basic quality-of-life improvement. I might be crazy but this issue did not seem to occur when I installed the 25.02.0 universal apk so I thought it had been fixed, then became an issue again when I switched to the gplay version, and now occurs even with the universal apk. However, when I had the universal apk installed, I still had element-android on my phone but disabled, and judging by a comment in #1923 maybe there's some weird interaction/interference going on between different matrix apps, but now I can't reproduce the conditions that seemed to prevent this issue.
Same here on Element X v25.02.0 with ntfy. This is a major issue in my opinion as it occasionally leads to double-notifications - one for desktop, one for mobile -, which in turn makes the usage of the mobile app almost unbearable.
This issue seems to have been resolved with the latest version 25.03.0 with the "SyncOrchestrator".
If that's the case, I might just kiss the person responsible for that patch. I will be eagerly waiting for v25.03.0 to appear on Google Play.