Possible bug in UI Event

[bogdyro]

Hi Martin. Found some strange behaviour with this trigger.
I'm having two triggers based on UI Event - announcement from the clock app (com.android.deskclock).
First one fires when notification on screen is displayed with text 'Alarm set for..'. Works every time apparently.
Second one should work when other notification contains text 'Snoozing for..'. This on behaves strangely. When an alarm fires and i click snooze in the app's screen the trigger works despite the fact that the I can't actually see the notification on screen (screen is locked for example). However, when screen is unlocked and I'm using the phone while the alarm fires and I do see on the screen the notification 'Snoozing for...', the trigger DOES NOT fire. Which I think is strange and is maybe a bug.

Besides that, trigger Notification on screen displayed doesn't fire at all. So don't know what's really happening.

[Martin]

Hi,

Announcements are not necessarily executed when the app shows a notification on screen. The two things are unrelated (technically at least). I'm also not sure when an app issues an announcement. Maybe deskclock decides that it's not necessary to issue an announcement when a notification button was pressed or another form of information was shown. The trigger Notification on Screen Displayed seems to work for me when the display is unlocked and the regular notification on screen with the round corners is displayed. On a locked phone I get a totally different UI that does not display a notification on screen at all.
Using trigger UI Event for situations where an announcement is shown and a second trigger Notification on Screen Displayed for the case where the device is unlocked seems to work on my device.

Maybe a completely different way to detect snoozing could also work: Condition for disabled alarm

Regards,
Martin

[bogdyro]

Great, I'll utilize both triggers. Thanks