-
-
Notifications
You must be signed in to change notification settings - Fork 51
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 13.6: Camera and Microphone permissions still cause crash #404
Comments
I don't know why this happens. I didn't change anything related to permissions recently, so it might be a change in new Firefox or macOS version. Can you test if this also happens with other websites that use camera and microphone. Also, can you submit the crash report to Mozilla and link the URL here (you can probably find it in |
Same problem occurs on https://meet.jit.si I am not sure how to report this to Mozilla. If I open either site with the standard Firefox build, it works. The problem seems to be in the trigger over permission management. In fact, if we can find a way to directly enable microphone/camera in the profile without going through the UI, I think that would be a workaround. |
I found a workaround - only needs to be done once at installation of the Google Meet profile, so maybe it can go in the FAQ and we can call it a day.
|
I tested it on https://meet.jit.si/ on my macOS VM and it doesn't crash, and I get a permissions prompt from macOS. I don't get any sound though, but this is probably caused by VM or my old macOS version. Can you also test on a different computer? I'm still not sure why this happens. Those permission entries in I now added this to the FAQ. |
I have an update for the FAQ, as the process given earlier no longer works, and needs a variation. Replace steps 4 and 5 with the following:
|
I would like to reopen this as it is occurring again on Google Meet. I am a new user of this extension on Mac OS 13.6. Installing Google Meet into a new profile and trying to turn on Microphone and Camera causes it to crash.
Originally posted by @aiyagari in #207 (comment)
The text was updated successfully, but these errors were encountered: