macOS permissions
Mavster needs four macOS permissions — Accessibility, Automation, Screen & System Audio Recording, and Local Network. This page covers what each is for, how to grant it, and how to verify the state.
Mavster needs four macOS permissions before it can drive your simulator and discover physical devices. Grant them all in System Settings → Privacy & Security.
What Mavster asks for, and why
Accessibility
Lets Mavster control simulator windows so screenshots and gestures land in the right place.
Grant it at: System Settings → Privacy & Security → Accessibility → toggle Mavster on.
Automation
Lets Mavster drive the Simulator app during test runs. macOS shows two one-time prompts the first time Mavster needs this — one for Simulator, one for System Events. Click Allow on both.
If you accidentally clicked "Don't Allow", flip them back at System Settings → Privacy & Security → Automation → expand Mavster → toggle Simulator and System Events both on.
Screen & System Audio Recording
Lets Mavster see your simulator's screen — the captured frames are what every visual step reads from.
Grant it at: System Settings → Privacy & Security → Screen & System Audio Recording → toggle Mavster on.
After toggling Screen & System Audio Recording, macOS may ask you to quit and relaunch Mavster.
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 gate still asks for it up-front.
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 the required permissions are 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 and confirm Mavster is toggled on under each of Accessibility, Automation, Screen & System Audio Recording, and Local Network. If you have multiple copies of Mavster (e.g. an older build in
~/Downloads), remove the stale entries from the lists — macOS may have associated the permission with the wrong copy.
