I have student who is currently facing this issue, and is unable to log on. She apparently has tried to access it in the Applications, and then right click to open it and it still gives the error message for her. Are you sure this is fixed for opening in Catalina?
Thank you for the quick response! The issue is the workaround isn't working for her. Is the latest development build the one that's readily available on the download site (3.4.2)?
For those still having this issue, try going to Security and Privacy in your System Preferences. Under General, it should say a similar message, but it should have an "Open Anyway" option.
There's another workaround you can use once that does not require opening MuseScore a special way every time
In Terminal run the following:
cd /Applications
xattr -d com.apple.quarantine MuseScore\ 3.app/
It's interesting to follow this thread. I think some MuseScore files may also cause problems while "playing" if the instruments used in the score don't have soundfonts which Apple approves of. This is a problem ( problem ...) with some DAWS, and it can be overcome for a while by resetting the Privacy to allow access to anything - even if only temporary. It may actually be a complete pain, as I think if there's a score with lots of instruments, this fix has to apply to each line/instrument. I'm not sure if this has hit Musescore, but I fear it might have done. This may not be the main issue here for others, but it's one I'm aware of, and it affects me.
Comments
Seems a reoccurence of #296799: MuseScore 3.3 can't be opened in macOS 10.15 Catalina, as far as I can tell @dmitrio95 is working on it, see https://github.com/musescore/MuseScore/tree/macos-notarization-issues
Apple turned notarization warnings into errors in February
Does the old workaround still work?
right-click MuseScore application and select "Open" in the pop-up menu
Assuming this is only macOS 10.15 and opening new installation not opening an installer.
I can't find the official workaround in the FAQ https://musescore.org/en/faq#faq-20592 any more. Assuming it was removed.
Having the MS version probably helps with the visibility and "dating" the issue
Attempting to install Musescore 3 on new MacBook Air running macOS Catalina 10.15.2
Old workaround does not work. I moved MS from downloads to application files. Still will not open.
See https://github.com/musescore/MuseScore/pull/5696
fixed in 9c5ca9c
Access it from the Finder, in /Applications. Click right on it. When it asks you if you really want to, click "open".
In reply to Access it from the Finder,… by Jojo-Schmitz
I have student who is currently facing this issue, and is unable to log on. She apparently has tried to access it in the Applications, and then right click to open it and it still gives the error message for her. Are you sure this is fixed for opening in Catalina?
In reply to I have student who is… by khwettstein
i have the exact same issue!
Use the latest development build then, or the workaround mentioned above your posts and in https://musescore.org/en/faq#faq-302904
In reply to Use the latest development… by Jojo-Schmitz
Thank you for the quick response! The issue is the workaround isn't working for her. Is the latest development build the one that's readily available on the download site (3.4.2)?
3.4.2 is a release, not a development builds. You'd find those also on the download page, but further down: https://musescore.org/en/download#Development-builds
In reply to 3,4,2 is a release, nit a… by Jojo-Schmitz
This is still not working for me, either by installing or by using the workaround.
Automatically closed -- issue fixed for 2 weeks with no activity.
What about Mac users who don't have a right-click option on their mouse?
In reply to What about Mac users who don… by murrayhazel1
All Mac Users have a "secondary click". Look at System Preferences > Trackpad and learn or set what it is. Or Control (not Command)-click.
In reply to Reoccurence of #296799:… by Jojo-Schmitz
It works
?
.
.
.
Sorry, too many duplicated comments. But it should still be a duplicate, shouldn't it?
This is the issue that got fixed (and later automatically closed), this is the one others are a dupicate off
#296799: MuseScore 3.3 can't be opened in macOS 10.15 Catalina is earlier?
But for a different MuseScore version, 3.3 vs. 3.4.2.
It got fixed, then broke again
In reply to But for a different… by Jojo-Schmitz
The workaround isn't working for me either. Same error message whether I try to open from the dock or from finder.
In reply to The workaround isn't working… by brandoncombs
Works for me and everyone else. Did you click RIGHT on it in the finder?
In reply to Works for me and everyone… by [DELETED] 1831606
Yes.
And you didn't see three buttons, one of which was "Open" (anyway)?
I am having this issue... the "work around" does not work for me. How can I open Musescore?
For those still having this issue, try going to Security and Privacy in your System Preferences. Under General, it should say a similar message, but it should have an "Open Anyway" option.
In reply to For those still having this… by katiecakesgal
Thank you for this!
In reply to Thank you for this! by choruskate
There's another workaround you can use once that does not require opening MuseScore a special way every time
In Terminal run the following:
cd /Applications
xattr -d com.apple.quarantine MuseScore\ 3.app/
In reply to There's another workaround… by music_by_jeff
It's interesting to follow this thread. I think some MuseScore files may also cause problems while "playing" if the instruments used in the score don't have soundfonts which Apple approves of. This is a problem ( problem ...) with some DAWS, and it can be overcome for a while by resetting the Privacy to allow access to anything - even if only temporary. It may actually be a complete pain, as I think if there's a score with lots of instruments, this fix has to apply to each line/instrument. I'm not sure if this has hit Musescore, but I fear it might have done. This may not be the main issue here for others, but it's one I'm aware of, and it affects me.
IIRC the MP3 export was affected by this too (and got fixed)