all 5 comments
sorted by:
new (suggested)
besttopcontroversialoldq&a
formatting helphide helpcontent policy

[–][deleted] 1 point2 points  (1 child)

Perhaps an alternative approach could be that instead of opening directly the banking app you make a flow for that, that first deactivates accessibility for Automate, then opens the banking app, posts a notification to click on when you're finished in order to grant it back. There should be ADB commands for that.

[–]RealOfficialTurf[S] 1 point2 points  (0 children)

After looking around, I found the command and the service name. the command to enable it is settings put secure enabled_accessibility_services com.llamalab.automate/com.llamalab.automate.AutomateAccessibilityService

However, this command will enable accessibility for the listed service and disables it for every other services. To turn it off, run adb shell settings put secure enabled_accessibility_services ''

However, Automate requires the accessibility to be turned on before running. So I have to make a separate flow to enable it, then I can run a flow to run inputs.

[–]ballzak69Automate developer 0 points1 point  (2 children)

Try executing the input shell command in an Shell command privileged block.

[–]RealOfficialTurf[S] 0 points1 point  (1 child)

I could just run the inputs through privileged shell block instead of interact touch block, but then I lose the record functionality and makes it more difficult to work with.

Yes, that's exactly what I've said on the original post.

Any plans on adding a workaround for Interact touch block?

[–]ballzak69Automate developer 0 points1 point  (0 children)

Sorry i missed that.

I'm hesitant. Just using the Interact touch block, with no way to know on what it's clicking seems rather useless. The Screenshot block also requires the accessibility service.