-
-
Notifications
You must be signed in to change notification settings - Fork 94
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 audio permission denied #176
Comments
Same issue on Linux using the WebCord-3.5.0-x64.Appimage so the issue isn't just limited to Apple I apparently missed the last release but I can confirm it was working in version 3.3.0. |
What I did is just enable the permission in the webcord settings... |
Huh, that's weird as it was working before. Totally solved my issue though. Thanks! |
The This is not a bug and because of that, it won't be worked on. |
WebCord is not usable in any mode without this I think. |
See #173, I need to resolve this first. The problem is through that I do not will to pay Apple to enrol in their developer program (or give any personal details) and I can't find any way to generate a certificate on my own. I believe this occurred on I believe that your PR would actually break the unsigned builds which are at least functional for Alternatively, there's a |
Actually, I will reopen this, from this description it might still be required to invoke this on macOS 10.14+. I won't however add any entitlements since the app is not signed (i.e. app will crash when requesting permissions when signed). |
Confirmed that 3.7.1 fixed it, tho the first time when asking for permission it shows and error page. Click allow then re-enable the mic worked. |
Aknowledgements
I have checked that there's no other issue describing the same or
similar problem that I currently have, regardless if it has been
closed or open.
I can confirm that this is not an issue with the Discord website,
but it is a problem specific to the WebCord itself. I have tested
if this bug occurs on Chromium/Chrome or any other Chromium-based
browser that uses unpatched/upstream Chromium engine.
I have tried running the build from the
master
branch and it doesnot have any fixes implemented according to my issue.
My issue describes one of the unstable and/or not fully implemented
features.
I have found a workaround to mitigate or temporarily fix this issue
in affected releases (please write it in Additional context section
below).
Operating System / Platform
🍎️ MacOS
Operating system architecture
aarch64 (64-bit ARM)
Electron version
19.0.7
Application version
3.4.0
Bug description
It should somehow ask user to turn on permissions in System Preferences -> Security & Privacy -> Privacy.
Additional context
No response
The text was updated successfully, but these errors were encountered: