Dismiss all notifications stops working after a while

[scatterthought]

Have you checked if an issue already exists for this bug?

• Nobody else has reported this bug before

Have you tried restarting your device?

• I have tried restarting my device and that did not help

What happened that you did not expect?

I've had the Dismiss All Notifications action working on my Samsung Tab S9 for a long time. When I updated Keymapper to the current release on Google Play, the action failed with a toast message "Denied notification access permission!" The Keymapper log says "Root access denied" when this happens.

There are no error messages reported in my keymap that uses the action, and Keymapper has Notification Access granted in the Android settings. My tablet is not rooted.

I tried rebooting and I tried switching to the beta program, but the problem remained. I then discovered that if I clear all data from the app and grant permissions again, the Dismiss All Notifications action will work for a brief period of time, then fail again with the same errors. The same thing happens if I uninstall and reinstall the app.

It seems to me that the app is losing notification access, even though Android still shows it enabled and the app doesn't detect that access has been denied. I've tried toggling Notification Access off and on again, but that doesn't fix the problem.

I trigger the action with a launcher shortcut, and there are no constraints.

Thanks for your great work!

What did you expect to happen?

I expect that Dismiss All Notifications will continue to work.

What would the developer need to do to reproduce the bug?

1. Make a keymap that uses the Dismiss All Notifications action with no trigger or constraints.
2. Check the "Allow other apps to control this key map with intents or shortcuts" option.
3. Create a launcher shortcut.
4. Test that the action works.
5. Test the action again daily until it stops working (it took about 24 hours to fail the last time).

I'm still doing more tests, and will add to this report if I gain more details.

App version

4.0.0-beta (and also the current Google Play release, which I think was 3.7)

Android version

Android 16

Device model and manufacturer

Samsung Tab S9

Extra info

• My device is rooted

[sds100]

Thanks for reporting this, it smells like the notification access service is being killed which is why it happens after a while. You've disabled all battery optimisations on your phone? Is there any red text in the log about errors?

[scatterthought]

Thanks for following up so quickly!

Battery optimization is disabled for Keymapper, and the action was working for about six months before it started failing after the recent update. I just checked the log and don't see anything besides the "Root access denied" error message, which I now realize is happening constantly.

At the moment it's still working. I use this action constantly, so I'll check the log as soon as it fails on me again. Anything else I should look out for? And to figure this out, would it be better for me to stick with the beta or return to the released version?

[sds100]

that root access denied error message is unrelated, its just useless spam which ive now removed. Your phone didnt update recently did it? Can you return to the non beta version and see if it still happens?

[scatterthought]

It's a Samsung Tab S9 tablet. The problem only started after an automatic update from Google Play, but I don't know how long of a gap there was before I noticed. It just stopped working one day. I think realized the app had updated due to the app notifying me of new features when I opened it to see what was going on.

I joined the beta program to see if the problem persisted. I'm now back on the 3.2.1 release and I'll keep observing it.

[scatterthought]

Accessibility failed again, but there's nothing in the log. Maybe I should roll back to the version before 3.2.1 to see if it happens there?

[sds100]

What do you mean accessibility failed?

[scatterthought]

Sorry, I meant notification access failed.

[sds100]

Can you try version 3.1 and see if it happens? There might be some other variable explaining why it started happening randomly. When was your phone last updated? Does it say in About phone in settings?