System Requirements

macOS permissions

Mavster needs one macOS permission — Local Network, for discovering physical devices. Simulators and emulators run with no permissions at all.

Mavster needs exactly one macOS permission: Local Network. Simulators and emulators are driven directly over their own device channels, so nothing about running tests touches Accessibility, Automation, or Screen Recording.

What Mavster asks for, and why

Local Network

Lets Mavster discover and communicate with paired physical iOS and Android devices over your local network (Bonjour). Not needed if you only test against simulators or emulators, but the setup screen asks for it up-front so physical-device pairing works the moment you want it.

Grant it at: System Settings → Privacy & Security → Local Network → toggle Mavster on.

How Mavster verifies the state

The permissions setup screen unblocks automatically as soon as Local Network is granted — there's no manual "I've granted it" button.

Troubleshooting

  • "Mavster opened but immediately shows the permissions screen and won't move on." Open System Settings → Privacy & Security → Local Network and confirm Mavster is toggled on. If you have multiple copies of Mavster (e.g. an older build in ~/Downloads), remove the stale entries from the list — macOS may have associated the permission with the wrong copy.
  • "I denied Local Network and now there's no prompt." macOS won't re-prompt once denied. Toggle Mavster on manually in System Settings → Privacy & Security → Local Network; if Mavster doesn't appear in the list at all, run tccutil reset LocalNetwork com.mavster in Terminal and relaunch.