-
Re: No Microphone access in development (Xcode cmd-r) builds
Suborbital Oct 19, 2018 2:06 AM (in response to kyb)use `tccutil reset Microphone` (the capital M is important!) to reset the user granted microphone permissions. then the xcode built version should ask you for permission again.
-
Re: No Microphone access in development (Xcode cmd-r) builds
dtissier Dec 20, 2018 9:33 AM (in response to Suborbital)This did NOT work for me. All it did was remove all the applications I gave access to from the Security & Privacy Microphone preferences.
-
-
Re: No Microphone access in development (Xcode cmd-r) builds
creed Jan 15, 2019 4:22 AM (in response to kyb)There seems to be two issues here: microphone access for both Xcode and the app itself.
Your app (or a UITest) can prompt (fail) for either or both, though not always on same run.
Both of these dialogs must be approved to allow access, after which the permission persists between Xcode and Simulator resets or restarts.
You can confirm access has been approved for Xcode in System Preferences -> Security & Privacy-> Microphone, where you should see the Xcode in the UI.
The app itself, approved or not, won't appear in the UI here, however.
If you are unsure it the app has been approved, reset all the microphone permissions with 'tccutil reset Microphone' in the Terminal, and re-run your app/test, until both dialogs have been shown and approved.
-
Re: No Microphone access in development (Xcode cmd-r) builds
alejandro171 Feb 5, 2019 8:39 AM (in response to creed)This didnt work for me. I am runint tests with xcodebuild for my app, and event though I granted access for a given simulator on a first run (where the tests succeded) on a second run I must grant access again, even if I am using the same simulator. Any clues??
-
Re: No Microphone access in development (Xcode cmd-r) builds
hotpaw2 Feb 6, 2019 8:51 PM (in response to alejandro171)If this is reproducable, then all of you should submit bug reports (see Report Bugs link below). Perhaps the Mohave sand-box security team and the Xcode team didn't talk to each other about this development scenario, and re-built debug builds are locked out.
-
-