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 audio permission denied #176

Closed
3 of 5 tasks
kklem0 opened this issue Jul 10, 2022 · 10 comments
Closed
3 of 5 tasks

macOS audio permission denied #176

kklem0 opened this issue Jul 10, 2022 · 10 comments
Assignees
Labels
type:bug Something isn't working

Comments

@kklem0
Copy link

kklem0 commented Jul 10, 2022

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 does
    not 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

Screenshot 2022-07-10 at 13 36 41

It should somehow ask user to turn on permissions in System Preferences -> Security & Privacy -> Privacy.

Additional context

No response

@kklem0 kklem0 added the type:bug Something isn't working label Jul 10, 2022
@kklem0
Copy link
Author

kklem0 commented Jul 10, 2022

@Scary-Guy
Copy link

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.

@ErikReider
Copy link

What I did is just enable the permission in the webcord settings...

@Scary-Guy
Copy link

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!

@SpacingBat3
Copy link
Owner

The entilements.plist seem to be only needed when the hardened runtime is enabled. WebCord currently does not support the signing and if you need to enable it, you need to update Electron Forge configuration accordingly.

This is not a bug and because of that, it won't be worked on.

@SpacingBat3 SpacingBat3 closed this as not planned Won't fix, can't repro, duplicate, stale Jul 24, 2022
@SpacingBat3 SpacingBat3 added status:invalid This doesn't seem right status:wontfix This will not be worked on labels Jul 24, 2022
@kklem0
Copy link
Author

kklem0 commented Jul 24, 2022

WebCord is not usable in any mode without this I think.
And that makes macOS not a supported platform anymore, and I'm not interested in making my own fork.
Would you merge it if I send a PR?

@SpacingBat3
Copy link
Owner

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 x64 as well and existed because of xattributes. A pull request #90 described the workaround for it.

I believe that your PR would actually break the unsigned builds which are at least functional for x64.

Alternatively, there's a universal package for macOS, but since it includes both x64 and arm64, it may have a double weight. Moreover, it may work exactly the same as standalone arm64 build.

@SpacingBat3
Copy link
Owner

SpacingBat3 commented Aug 1, 2022

Actually, I will reopen this, from this description it might still be required to invoke this on macOS 10.14+.
https://developer.apple.com/documentation/avfoundation/capture_setup/requesting_authorization_for_media_capture_on_macos?language=objc

I won't however add any entitlements since the app is not signed (i.e. app will crash when requesting permissions when signed).

@SpacingBat3 SpacingBat3 reopened this Aug 1, 2022
@SpacingBat3 SpacingBat3 removed status:invalid This doesn't seem right status:wontfix This will not be worked on labels Aug 1, 2022
@kklem0
Copy link
Author

kklem0 commented Aug 21, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants