Dialog Input cannot show on top of quick setting page after updating to Android 13.

87 views
Skip to first unread message

Cesaryuan

unread,
Aug 4, 2023, 1:54:42 AM8/4/23
to Automate
Reproduce Steps:

1. Create a flow like shown in video.
2. Run the flow.
3. Trigger the flow by quick tile.
4. As we can see, the dialog is hidden down the page.

Phone: Redmi K40, MIUI 14.0.7, Android 13

bandicam 2023-08-04 13-52-01-555.mp4

Henrik "The Developer" Lindqvist

unread,
Aug 4, 2023, 7:50:28 AM8/4/23
to Automate
I suspect the "notification shade" area where Quick Settings tiles and notifications are shown has always been shown over apps.
Anyhow, use the Interact block with action "Dismiss notification shade" before the dialog.

Cesaryuan

unread,
Aug 6, 2023, 4:51:57 AM8/6/23
to Automate
Thanks for your reply! As I can see, before the Android 12, the "notification shade" is shown under the dialog. 😂

I tried the Interact block with action "Dismiss notification shade", but it seems not work. Maybe the parameters is not correct?

tmp684B.pngtmp389C.pngtmp7B92.png

Shari Shark

unread,
Aug 6, 2023, 5:09:54 AM8/6/23
to automa...@googlegroups.com
Not sure if this is the answer but as you're running miui, this might be the answer.

Try to enable this setting.
System Settings → Apps → Automate → Other permissions → enable Display pop-up windows while running in the background



Look at this page for more info.


--
You received this message because you are subscribed to the Google Groups "Automate" group.
To unsubscribe from this group and stop receiving emails from it, send an email to automate-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/80083989-93ed-4659-9719-1a38a2a29e16n%40googlegroups.com.

Cesaryuan

unread,
Aug 6, 2023, 5:44:27 AM8/6/23
to Automate
Thanks! I checked that the permission has been enabled🤣. Anyway, thanks for your advice!

Henrik "The Developer" Lindqvist

unread,
Aug 6, 2023, 6:27:06 AM8/6/23
to Automate
According to the log the Interact block is unable to perform the action, i.e. it takes the NO path, so the Input dialog block is never executed.
Ensure the Automate accessibility service is running, this can sadly be difficult due to Android bugs causing it to be killed/stopped then not restarted properly. Especially on the Chinese devices withe their broken Androids, exclude Automate from every "power save" feature, see: https://llamalab.com/automate/doc/faq.html#automate_not_running
Just tested such a flow and it works just fine on standard Android 13, assuming the Accessibility service is running.
Reply all
Reply to author
Forward
0 new messages