Catching Automagic's own persistent notification

[Wibbly]

I have a flow to snooze the Automagic notification it used to work when the phone boots but now isn't triggered unless I manually stop and restart the Automagic service. Using Oreo 8.1. Anyone know of a fix?

[Desmanto]

Did the flow get triggered? Check the log for the time. It seems to be the Trigger Automagic Startup didn't work properly. But when you stop/restart the service, it works. The culprit must be something related to the phone doesn't give signal to Automagic on boot.

What phone do you use? Does it have startup manager? MIUI-ish ROM usually has this feature and will block the app from auto start. You need to find the setting which manage the auto start and enable/whitelist for Automagic. Usually it is at permission setting, mobile manager, mobile security, startup manager or similar wording.

[Wibbly]

It triggers from the "Automagic service is running" notification appearing (when it works) - I don't use Automagic startup as a trigger. And it's "Automagic service is running" notification that's snoozed. It used to work. I have a Pixel 2. It's as if there's a race condition when Automagic starts and it doesn't catch its own notification any more, maybe since the latest monthly Oreo security update?

But once Automagic is running after a boot is complete, the flow does trigger if I then stop the Automatic service and then restart it (from within the Automagic menus). So something different seems to be happening at boot time compared to when the flow was reliably triggered at boot time...

Up until now this flow has been effective at hiding the Automagic service notification in the notification shade completely automatically. Now it requires manual intervention to stop/restart the Automagic service whenever the phone is restarted

[Desmanto]

Oh, why don't try to use Automagic startup as trigger instead? But maybe you have to add sleep 2-5 seconds to make sure the notification appear completely, to be snoozed.

[Wibbly]

Ok - I have now created a work-around that seems to work on first testing

I now also trigger the flow using Automagic Startup trigger, and I have added a Notification on Statusbar Displayed condition that looks for the notification (like the one in the Notification on Statusbar Displayed trigger above).

I still don't understand why the original flow broke though....