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 - MuseScore "is damaged can't be opened" #118

Open
scorster opened this issue May 18, 2023 · 14 comments · Fixed by #294
Open

MacOS - MuseScore "is damaged can't be opened" #118

scorster opened this issue May 18, 2023 · 14 comments · Fixed by #294

Comments

@scorster
Copy link

scorster commented May 18, 2023

Issue type

Crash or freeze

Bug description

For months I've been running v3.7.0.4524440406 on Mac OS Ventura 13.3.1

macOS 10.16, Arch.: x86_64, MuseScore version (64-bit): 3.7.0.4524440406, revision: github-musescore-musescore-f3d36a3

I'll start by saying I'm deeply appreciative of all the work dedicated to making 3.7 exist!

Today I tried to install the latest version but got the error that MuseScore "is damaged can't be opened"

MuseScore is damaged and can't be opened v64284

After that I downloaded a revision a few versions back, but I got the same alert with 44930:

MuseScore is damaged and can't be opened v44930

Any special steps required to get beyond this?

Is this perhaps related to the unsigned issue which I overcame when first opening v40406?

Thanks!

Scorster

Steps to reproduce

  • Download from Jojo's Actions page
  • Unzip
  • In the installer window drag MuseScore to the "Applications" folder shown
  • double click the installed version of museScore in the Applications folder

Screenshots/Screen recordings

No response

MuseScore Version

Never opens.

Regression

Choose option...

Operating system

MacOS 13.3.1

Additional context

No response

@Jojo-Schmitz
Copy link
Owner

Might have been caused by the forced move to a newer macOS build system and XCode.

@knoike
Copy link

knoike commented May 18, 2023

https://discussions.apple.com/thread/253714860?answerId=256963522022#256963522022

xattr -c /path/to/MuseScore.app

It might work this way.
This is a not good way from a security point of view, but I think it works as a workaround in this situation.

@Jojo-Schmitz
Copy link
Owner

Reported as fixed in https://musescore.org/en/node/342126#comment-1194631 after xattr -c /path/to/MuseScore.app

@Jojo-Schmitz
Copy link
Owner

@scorster can you re-check?

@scorster
Copy link
Author

Sure, I'll see if it works.

What's the direct link for the current MuseScore 3.7 MacOS download?

scorster

@Jojo-Schmitz
Copy link
Owner

@scorster
Copy link
Author

scorster commented Jun 27, 2023

Hi Jojo,

I don't entirely know my way around this neighborhood, but I downloaded "MuseScore 3.7.0.5378956140 Devel"

I get the same "damaged" alert as posted at the start of this thread.

Mac OS Ventura 13.3.1(a)

scorster

@Jojo-Schmitz
Copy link
Owner

Jojo-Schmitz commented Jun 27, 2023

Hmm, pity...

Even after that xattr -c /path/to/MuseScore.app?

@RickyRister
Copy link

Also ran into the same issue. The xattr fix worked.

@Jojo-Schmitz
Copy link
Owner

Does the artifact from #93 work? It uses Qt 5.9

@RickyRister
Copy link

No difference.

@Jojo-Schmitz
Copy link
Owner

Jojo-Schmitz commented Jan 30, 2024

So it doesn't depend on the Qt version used.

But the xattr still works, right?

What about the PR artifacts (for Mu4) on the upstream repo, they are not notarized either (only the nighly builds are), do they work regardless? Or do they need that xattr too?

I wonder whether I can make that xattr part of the build process.
Hmm, no:

When an application gets downloaded from any source other than those that Apple seems suited, the application gets an extended attribute "com.apple.Quarantine". This triggers the message: " is damaged and can't be opened. You should move it to the Bin."

So it needs to be done on the target machine, after the download and install.

@RickyRister
Copy link

RickyRister commented Jan 31, 2024

But the xattr still works, right?

Yeah, xattr still works in letting me open the app. The playback is still greyed out and unusable.

What about the PR artifacts (for Mu4) on the upstream repo, they are not notarized either (only the nighly builds are), do they work regardless? Or do they need that xattr too?

downloaded this artifact https://github.com/musescore/MuseScore/actions/runs/7718288564

I'm getting “MuseScore 4.3.0.240302229 Devel” cannot be opened because the developer cannot be verified. instead of the quarantine message when I try to open it, which is the expected message to get when downloading apps from the internet. I bypass it as normal by right clicking open. The app works (The sound isn't broken or anything).

tl;dr: it works as expected

Yeah, maybe notarization isn't the cause after all.

@Jojo-Schmitz
Copy link
Owner

#294 doesn't solve this, as I can't notarize.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants