-
Notifications
You must be signed in to change notification settings - Fork 36
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
Notifications sometimes become un-dismissable #2281
Comments
Hi, @JonDum, Thank you for bringing this to our attention. Apologies for the inconvenience. Our dev team is currently investigating the issue; unfortunately, we have not been able to reliably reproduce it on our end. In the interim, we suggest resolving this issue by restarting the launcher: |
It seems to only happen with Twitter at the moment. This bug is actually way more annoying than the last because it seems to happen much more frequently and I end up having to restart Niagara over ten times a day. Let me know if I can get you any logs that might help narrow it down. |
This happens to me too. Affected apps are Spark mail and Google messages in my case. I am using Pixel 4a(5g) with Android 13. It started with Niagara 1.9.8 (maybe 1.9.7 but I skipped this one). |
It seems that for me it happens only to apps which are in others apps pop-ups. E.g. WhatsApp notifications were working properly, but once I moved it into a pop-up, the issue occured. |
Workaround: A user on Discord found a workaround to this bug, but it requires you to constantly tap outside the popup. https://discord.com/channels/728630549278883950/1122390595948789791/1122426805547171850 |
Any update on this? I still have to hard restart Niagara almost every day. |
Which Niagara version are you using? I am not experiencing this issue for a long time. |
Describe the bug
Similar to #2192, but now notifications cannot be swiped away. They become our of sync with the notifications in the system tray. Using latest version 1.9.5
Steps to reproduce
Currently unsure what exactly gets it to this state, but it occurs frequently after continued use.
Does the issue also occur with other 3rd-party launchers?
Not applicable
Other 3rd-party launcher(s) tested
No response
Device name
Pixel 7 Pro
Android version
Android 13
Screenshots / Screen recordings
https://mega.nz/file/oJcxSBxC#FCNBk5O8KJeSz8Dx70Tls8a_s29hswrQ0RwGsKOUOmE
The text was updated successfully, but these errors were encountered: