Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MacOS Mojave - camera and microphone access not requested #122

Open
oori opened this issue Feb 7, 2019 · 4 comments
Open

MacOS Mojave - camera and microphone access not requested #122

oori opened this issue Feb 7, 2019 · 4 comments

Comments

@oori
Copy link

oori commented Feb 7, 2019

Symptom
Building from sublimetext works but:

  1. The build process is very slow.
  2. The app runs extremely slow, unusable. Processing runs at 0.x FPS
  3. camera and microphone not working

Test
Running the same processing-java ... command from terminal works fine !
On first run Mojave asks for permissions to access camera and microphone.

If you then go to Mojave system preferences --> Security & Privacy --> Privacy --> camera/microphone and revoke that permission (uncheck the box to disallow terminal/iterm access), and try to run the processing-java ... again, you'll get exactly the same results as if building from sublime text (ie. slow, unusable). I'm pretty sure you can do the same test with processing as well.

Conclusion
When running a patch that requires camera or microphone access, on first use, the user should get a prompt from Mojave.

Problem
When building from sublimetext, the "request access" box never appears. and there's no way to manually add apps to the camera/micropohne list in Mojave.

Bypass
Right now I'm just building from terminal to bypass this, but I'd be happy to build from sublime text again.

Any idea how to resolve this?
Thanks

@ybakos
Copy link
Collaborator

ybakos commented Feb 7, 2019

Thanks for the bug report @oori . I'll take a look as soon as I can.

@maerzhase
Copy link

+1 same issue. would be cool to get this working again via sublime build

@gregtreadwell
Copy link

+1 on this issue as well.

@sublimeconfusion
Copy link

+1
I've had this problem before when I had updated my OS. I fixed it that time by copying over an older version of the "TCC.db" file from another machine. However, it's happened again since updating sublime and now I'm trying to find a work around again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants