-
Notifications
You must be signed in to change notification settings - Fork 522
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] “YouTube Music” cannot be opened because the developer cannot be verified. #186
Comments
I'm not very expert about MacOS, but if I remember correctly, you can open the app without this error (after installation) with right click on the app (I don't know if you have right click enabled, anyway, you need to open the action menu) and click "Open". |
Sorry for the late response. it worked, I did not have a new update at that moment... Weird macOS... Thank you for your help! |
This should be in pinned in issues or discussion as mac os fix. Thanks @andreiropotica this always helps after reinstall. |
see this link: https://github.com/th-ch/youtube-music#macos |
btw if I get it correctly, fix it fully (so users wouldnt need to do anything) the project would need its own developer account, which costs 99 dollars per year (and the app could be also in the store) |
Does anyone know why this command works? |
I'd assume |
I saw someone recommend this similar command for another app, it apparently just tells macOS to let you open it despite the creator/app being unverified/unsigned. Take this with a grain of salt because I'm only recalling from a Reddit thread on the Zen browser |
Thanks for saying what I already said? |
geez sorry |
Ok I came off way too rude. I won't give excuses, I was just confused by the GitHub notification I received. |
Ah, sorry for the notification |
Hello!
I am getting after first install and after todays update the folowing error on opening the app:
The workarround/solution I found was executing:
xattr -d com.apple.quarantine /Applications/YouTube\ Music.app
after each install/update.Is there another way to avoid this error on the next update?
Thank you very much for all your hard work!
Andrei
The text was updated successfully, but these errors were encountered: