1
Solved

Notification removed event documentation

The help text for the Notification Removed event states that it doesn't work for Tasker-generated events. My testing tells me that this is not true, it doesn't work for notifications created by the same app that created the notification in the first place, not only Tasker. IMHO it should work as documented, letting kid apps react on the removal of their own notifications. As it is now a plugin, free or paid, is required in addition to the kid app to achieve this, which doesn't make sense. This is particularly important in Android 14+ where Google have taken away the possibility to create "permanent" notifications, so to overcome this the app itself needs to reinstate such notifications themselves. But now a plugin is required which is NOT good. Thanks for listening. 

1 reply

Hi. The documentation says "Tasker" but it should actually say "its own".

Being triggered by its own notifications has a very high risk of creating infinite loops. Since you know when you're cancelling notifications, you can simply do your actions then.

I'll fix the documentation.

Hope this clarifies it!

Topic is closed for comments