Uiautomator and AccessibilityServices conflict when using Maestro

[JaimePaton]

When trying to finish the onboarding for our application [Qustodio] it appears to be a conflict between Uiautomator and AccessibilityServices. https://stackoverflow.com/questions/29035320/are-uiautomator-and-accessibilityservices-not-compatible

Steps to Reproduce

1. Download and Onboard Qustodio using Maestro

Actual Behaviour
Onboarding cannot be completed due to conflict with the Accessibility permission.

mon_mar_23_2026_root_cause_analysis_of_maestros_accessibility.md

You can see the issue occurring in the video here: https://drive.google.com/file/d/1aJe-SB6QqlaNdOYpzsjDH1NIFNxoIQaj/view?usp=sharing

maestro-studio-logs.zip

[linear]

MAE-420

[Fishbowler]

You might need to provide a little more info. No clue what that app is.

We're not aware of any device conflicts at all.

Could be that the app requests a system permission that we don't support.

[JaimePaton]

The application is a parental control application. So we request a number of permissions to allow us to function.

Which system permissions don't you support?

[Fishbowler]

https://docs.maestro.dev/maestro-flows/flow-control-and-logic/permissions - generally we support app permissions not system permissions. But you can absolutely write a flow that goes and taps the right buttons to enable system permissions.

[JaimePaton]

This is where I discovered the issue. I've created a flow to complete the onboarding of our application which includes granting a number of system permissions on the device. However when I grant our final permission - it prokoves our detection for an permission not being active, in this case accessiblity erroneously. If I do this manually, it functions correctly.

[Fishbowler]

Maestro won't alter the permissions after app launch. If your onboarding grants a permission correctly, then Maestro won't alter that

[JaimePaton]

I've spoken to our developers and it looks like it is provoked by our application and we have a bug report open now. I will close this now. Thanks for the quick responses.

[JaimePaton]

So our developers have had a look at this and it appears to be a conflict between Uiautomator and AccessibilityServices. https://stackoverflow.com/questions/29035320/are-uiautomator-and-accessibilityservices-not-compatible

mon_mar_23_2026_root_cause_analysis_of_maestros_accessibility.md

You can see the issue occurring in the video here: https://drive.google.com/file/d/1aJe-SB6QqlaNdOYpzsjDH1NIFNxoIQaj/view?usp=sharing

[Fishbowler]

If it's a conflict between Uiautomator and AccessibilityServices, I'm not sure it's something that Maestro can solve. I'm happy to leave the issue open, but I don't think this is something that will reach the top of the priority list for staff in the near future.

[Fishbowler]

In the meantime, if you're hoping for another community member to pick up your issue, update the title and description to describe the issue, and provide the best errors and reproduction that you can. Being descriptive means you're more likely to hit others searches.