-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Audible ping but no badge on notifications for bot messages #25904
Comments
Additional context: Element Android shows a notification for the bot messages if the room is set to notify for all message. |
@davidegirardi what version are you on? there's multiple changes in the area of notifications happening with every recent release. |
I have Element version: 1.11.36 Olm version: 3.2.14 and Element Nightly version: 2023080101Olm version: 3.2.14 running in parallel. Nightly had the sound turned off. I'm turning it on and turning off the sound for production and see what happens. |
There shouldn't be any differences in handling of audible pings, but definite changes to notification badges happening frequently. Things also depend on your specific push rules in account_data |
Then there was no difference today. Nightly had issue with badges not showing up a few days ago but everything seems OK now. |
That was #25881 |
Nightly works as expected: no ping and just a dot for bot messages. See also: #25794 (comment) if your notification stop pinging at all and you run the notification settings beta. |
Your use case
My default notification settings (new version) look like this:
If I set a room to notify for "All messages", when a bot writes a message I get an audible ping but no badge counter.
I don't know if it's related on the new notification settings or if it has always been like that. I do remember hearing pings with no counters before but never found an explanation until now.
I'd expect to either get a badge or no notification for bot messages at all.
Have you considered any alternatives?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: