Has anyone been able to run MuseScore 3.7 on MacOS?

• Mar 26, 2023 - 07:04

I successfully downloaded MuseScore 3.7. It's an unsigned app so the first step was to register MuseScore 3.7 as an exception on my Mac, per Apple's instructions.

That allowed me to initiate a launch under MacOS 13.2.1 ... but then MuseScore 3.7 abended.

On reviewing the crash log Jojo noted the missing Qt library ”QtWebEngineCore”. He said it "Might be a bad packaging," but that would be hard to determine, as he doesn't have a Mac.

So I'm wondering: Is anyone successfully in running MuseScore 3.7 on MacOS. If so, how?

One proposed workaround is to launch MuseScore 3.7 from the Terminal command line with -w. That should prevent MuseScore from accessing the web, hence no need for that missing library.) I've tried an failed various ways of launching 3.7 from the command line, without success. Can anyone offer a command that works?

Another proposed workaround is to install Qt 5.15.2 on my system. I’d only want to install Qt if I’m going to start using it—and that seems unlikely anytime soon. All to say, I haven't tried this approach.

Anyone?

scorster

Comments

• Mar 26, 2023 - 17:34

On your advice I attempted to start 3.7 by dragging a score onto it provoked the same crash.

I'm in unfamiliar territory with the Terminal but tried that approach.

Don't know if I have the part after \ correct.

    • Need a different file name?
    • Need a space before 3.app?
    • Since the handbook used a capital F I used a capital W:

JBs-mb-5:~ John$ /Applications/MuseScore\3.app/Contents/MacOS/mscore -W

/Applications/MuseScore\ 3.app/Contents/MacOS/mscore -W
dlopen error : dlopen(libjack.0.dylib, 0x0001): tried: 'libjack.0.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OSlibjack.0.dylib' (no such file), '/Applications/MuseScore 3.app/Contents/Frameworks/libjack.0.dylib' (no such file), '/Applications/MuseScore 3.app/Contents/Frameworks/libjack.0.dylib' (no such file), '/usr/lib/libjack.0.dylib' (no such file, not in dyld cache), 'libjack.0.dylib' (no such file), '/usr/lib/libjack.0.dylib' (no such file, not in dyld cache)
dlopen error : dlopen(/usr/local/lib/libjack.0.dylib, 0x0001): tried: '/usr/local/lib/libjack.0.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/lib/libjack.0.dylib' (no such file), '/usr/local/lib/libjack.0.dylib' (no such file)
Unknown option 'W'.

Then I tried a lowercase -w:

-bash: /Applications/MuseScore3.app/Contents/MacOS/mscore: No such file or directory

Reply

• Mar 26, 2023 - 17:29

Hi Jojo,

Thanks for all this!

I'm only casually familiar with Github. So I'm unclear.

Are you saying there's a pending build, or is there a current build of 3.7 for MacOS that addresses the issue in pull 93? If there's a current build, is there a link to the build zip file at the link you provided? Or can you post a direct link to build file?

Thanks!

scorster

Reply

• Mar 26, 2023 - 17:53

It works!!

Just one temporary glitch: Initially there was a prolonged hang at the MS 4 update advertisement dialog. Clicking OK wouldn't dismiss it and I couldn't do anything else. After about 20 seconds that rectified. And thankfully, since the second launch of 3.7 I can immediately dismiss the advertisement.

I was surprised that only the default plugins don't show in the Plugin Manager. 3.7 has its own plugin repository?

Again, thanks for all this Jojo!

scorster

Reply

• Jun 16, 2023 - 12:51

New artifact (using Qt 5.9) at https://github.com/Jojo-Schmitz/MuseScore/actions/runs/5289563906

Edit: no longer the above, but now at: https://github.com/Jojo-Schmitz/MuseScore/actions/runs/6855313675
Edit 2: feel free to ping me for updated versions

But also try the one from https://github.com/Jojo-Schmitz/MuseScore/actions/runs/5288485843, it uses Qt 5.15.2 but has some Mac specific compilation fixes

Reply

• Feb 1, 2024 - 05:08

Thanks for your continuing efforts on this Jojo.

I downloaded MuseScore 3.7.0.7709149398 Devel.app and I'm sorry to report that MacOS Ventura (13.5.2) still gives the so called "damaged" alert.

      MuseScore 3.7.0.7709149398 Devel.app_.png

I tried the instructions from appletoolbox.com

      Allow apps downloaded from - Anywhere.png

... but there was no Anywhere option in Privacy and Security >Security

I tried the next recommendation on that page, which was to ** Add The App As a Developer Tool** but:

   a) when added MS 3.7 to the "developers" list identified it as MuseScore 4
   b) double clicking MuseScore 3.7.0.7709149398 Devel.app still provoked the "damaged" alert

  .  .  . 

I also tried the first set of instructions from iboysoft.com but there was no Open Anyway button:

      Is Damaged - Open anyway button.png

I did not try the Terminal options suggested by either website, and I'd rather postpone that until someone with more Terminal experience can confirm that it works and provide a list of possible caveats.

Thanks!

scorster

Reply

• Feb 14, 2024 - 04:24

> @ jdaniel220 • I'm running Sonoma 14.1. I've tried several different installations [off of MS 3.7] from GitHub, and I keep getting the "damaged" alert too.

Sorry to hear that. I'm dead in the water here with the latest MS3.7 builds.

Early on, and though it was challenging to install, I eventually I got the March 26, 2023 MuseScore 3.7 version running on MacOS Venture 13.5.2:

   MuseScore version (64-bit): 3.7.0.4524440406, revision: github-musescore-musescore-f3d36a3

Can't remember the steps off the top of my head, but it was from the advice in this thread.

Please keep us posted on your progress. I'd really like to be able to use the latest builds. Mine is nearly a year old.

scorster

Reply

• Feb 14, 2024 - 14:12

Thanks for the info! I may try one of the earlier versions. I've been seeing elsewhere that the "damaged" file warning sometimes owes to security features on Mac, and you can experiment with turning off some of these protections and then open it. Not sure, but I'll keep trying.
Thank you!

Reply

• Feb 14, 2024 - 19:12

thanks for your help! I did try the steps in the above link. It seems that I can run 3.6 builds going through the steps suggested. (All went just as described in the link--got an error message but ignored it, control-clicked the app icon to open it anyway and indeed it did open and run fine.)
However, it seems I can't run the 3.7 builds. I keep getting the error message and it just won't open...

Attachment Size
Screenshot 2024-02-14 at 2.10.02 PM.png 93.03 KB

Reply

• Feb 14, 2024 - 19:57

I also tried the instructions in the link above.

Got the expected "damaged" alert. Then I followed the instruction to Cancel and Right-click>Open
Here on MAcOS Ventura 13.5.2 that provokes the same alert.

Thanks for staying on this.

These are Apple's official "consumer" instructions for this sort of situation:

     https://support.apple.com/en-us/102445

But the Open anyway choice does NOT in my Security panel;

Apple's support page shows the Open Anyway option:

     Privacy and Security _ Open Anyway.png

The following image shows Open anyway missing on my system. Maybe there's some Security setting that enables that security option?

     Privacy and Security _ NO Open Anyway.png

scorster

Reply

• Feb 16, 2024 - 20:34

Jojo-Schmitz wrote> Does xattr -c /path/to/MuseScore.app help?

Yes. Thanks Jojo. Another step forward!

I ran the xattr-c terminal command on MacOS 13.5.2 and it successfully removes the quarantine attribute from MuseScore 3.7.x

So now MuseScore indeed opens and appears to operate normally, with one big exception: There's no playback:

     • The playback controls are disabled (grayed out.)
     • And the I/O>PortAudio menus are empty (in Preferences>I/O)

MuseScore 3.7 MacOS Ventura preferences IO.png

Reply

• Feb 19, 2024 - 20:04

Jojo-Schmitz wrote > Well, this doesn't seem to be related to notarization.

Correct. It appears I've hurdled the notarization issue.

Nevertheless less that previous post is related to the opening title: "Has anyone been able to run MuseScore 3.7 on MacOS?"

I'm a huge fan of your ongoing efforts and what you've accomplished in MuseScore 3.7 Evolution.

And I'm hoping someone can help with the Playback issue on MadOS. I'm certainly wondering if anyone else has encountered it. I've never had a I/O Preference issue on any previous installation.

Reply

• May 21, 2024 - 10:22

Just checked out the latest build (Treat svgz file as a vector image #2407).
Still no sound, BUT I found the following comment in the annotations:
build
No such keg: /usr/local/Cellar/portaudio
Would that possibly help to solve the sound problem on MacOS?

Reply

• May 28, 2024 - 18:17

I was able to get it to run, but it took some digging, and I just use a Mac; I don't know a thing about them or computer programming in the least. I've listed the how-to's for each. For me it was #3 that worked. Report based on my system, which is Ventura 13.3.

There seem to be three levels of fix you can go for. This is the order I went in, which seemed least fiddly to most fiddly.

1) tell Mac OS to allow you to open apps from anywhere;
2) add the software as a "Developer Tool"
3) remove the quarantine flags from the software.

1) Tell Mac OS to allow you to open apps from anywhere.
System Settings → Privacy & Security: Security (near the bottom). Choose the radio button "Anywhere" for "Allow applications downloaded from".

Ventura's System Settings/Privacy & Security on my computer didn't already have that option, but there's a terminal workaround that will put that button there for you. Instructions are edited from from a website where learned this.
1. Quit out of System Settings if it is currently open.
2. Cut and paste this command into Terminal: sudo spctl --master-disable
.
3. Press "return", enter password as prompted.
4. Return to System Settings. The option will now be there.
5. Try running MuseScore.

2) Add the software as a "Developer Tool".
Assuming you have installed MuseScore Evolution,
1. Go to System Settings/Preferences → Privacy & Security → Developer Tools (near bottom)
2. Use the " + " button to add MuseScore "Allow the applications below to run software locally that does not meet the system's security policy"
3. Try running Musescore again.

3) Use the "xattr" command to remove the quarantine flag from the MuseScore build that the system claims is damaged. The website where I got this advice recommends this as a last resort. It happens to be the one that worked for me.
1. Cut and paste this command into Terminal: xattr -r -d com.apple.quarantine
2. Enter the path to MuseScore. (Drag/drop the MuseScore's icon to Terminal's cursor does this.)
3. Press "return".

If Terminal says it's not allowed to do the operation, type "sudo", space and then repeat the syntax above with the pathname. It will then prompt you for a password. This is what I ended up doing, but now it runs on my computer.

Reply

• May 28, 2024 - 22:45

I wish I got it to play. I got as far as the xattrib part of the thread (this very same one) and realized I wasn't emotionally ready to go back to terminal, especially on a guess that it might work. I'm too much of a novice—not even novice, really—when it comes to code-level things. If it's a proven solution to get the audio running (I'd love to hear where my errors are in the score, because it's lute tablature, not notes), I'd be all over it. So, did I miss anything? Is this solved? If not, are the geniuses at GitHub on it?

Oh man, you said "say" as an interjection in your note. I love, love, love it! It's like meeting Cary Grant on a message board. —R

Reply

• May 29, 2024 - 19:15

Hi Jojo, do you mean that you'd like me to post the solution on the Issues section for Evolution on GitHub? I apologize for being so thick about these things, but I can barely grasp what a wiki is or how to use one. I might end up being very clumsy about it, if that's okay.

Meanwhile, thanks for being such a great and patient advocate on this forum. Not to mention your programming gifts! Evolution saved my ability to continue work on a project while MS4 kept stalling my progress with various instabilities.

Reply

• Sep 14, 2024 - 03:27

Here are the steps I've taken to try to get MuseScore 3.7.0.10717483411 running on my Mac.

I downloaded MuseScore-3.7.0.10717483411.dmg for MacOS 13.5.2.
OS: macOS 13.5, Arch.: x86_64, MuseScore version (64-bit): 3.7.0.10717483411, revision: 495c4d4

After installation the MuseScore application (MuseScore 3.7.0.10717483411 Devel.app) is in my main applications folder (not my User Applications folder.) And as expected, double clicking the app provokes the "damaged app" alert.

To render the app viable—by removing the quarantine via a Terminal xattr -c command—I opened the Terminal utility and entered following at the Terminal prompt:

    • John$ xattr -c (note that I included a space after the c
    • then I dragged the MuseScore app from the applications folder to the Terminal window. That step added the directory path to the command, yielding this:

           John$ xattr -c /Applications/MuseScore\ 3.7.0.10717483411\ Devel.app

    • Then I pressed return
    • I double-clicked tthe app to open it

Now there's no alert ... but the 3.7.10717483411 app never opens. when double-clicked

However, it opens if I drag a score onto its app icon. It appears to operate normally EXCEPT there's still no audio because no sound devices show in the MuseScore>Preferences>I/O>Port Audio>Device.

Please advise.

scorster

P.S. Sorry, I was under the impression that the QT reversion will allow this 3.7.0.10717483411 to play audio on MacOS.

Reply

• Sep 14, 2024 - 03:49

BTW, originally I attempted an alternate solution by adding MS 3.7 to the Developers Tools list, as recommended above.

Two things struck me as odd:

1) In the Developer Tools panel I pressed the + button and chose MuseScore 3.7.0.10717483411. Afterwards I was returned to the Developers Tools panel, but didn't see MuseScore 3.7.0.10717483411 added to the list

2) I noticed MuseScore 4.4.1 listed Developer Tools. And I definitely did NOT add it to the Developers Tools list. Does MuseScore 4.4.1's installer change that setting??

Settings - Privacy and Security - Developer Tools MuseScore.png

Reply

• Sep 14, 2024 - 10:41

@Jojo-Schmitz wrote

> Pity, still no sound.

I know. And I appreciate your attempts to get recent versions of MS3.7 working for MacOS AND all you do for MuseScore and MuseScore Evolution 3.7.

Regarding Apple Silicon, yes I'm on a M2 MacBook Air.

I wonder if others can get the latest 3.7 running on non silicon Macs. Hopefully someone will report back!

Reply

• May 28, 2024 - 22:46

I'm a user of for Windows version, but I interested in this issue and its workaround.

I think that the workaround procedure you described seems like a good solution.
In particular, I'm interested in doing run command

"xattr -r -d com.apple.quarantine /path/to/MuseScore.app"

instead of

"xattr -c /path/to/MuseScore.app" .

After running this command, is your audio device available in MuseScore 3.7 Evolution ?
The recent version has a issue that the audio device is not available(not visible) from it.
https://musescore.org/en/node/347226#comment-1229390

Reply

• May 29, 2024 - 19:20

Nice to meet you ( はじめまして！). Zannen nagara—unfortunately—I have not found a solution to make audio run in Evolution. Any discussion I've come across on the topic has been too technical for me to understand whether the solution is simply proposed or proven.

Reply

• Sep 8, 2024 - 07:01

I might have come across a clue to why this version of Evolution doesn’t play audio. It does play just fine from the same install file on my old MacBook Peo running OS Mojave. Maybe it has to do with the later OS for Silicon/M1 chip architecture, which is what my main desktop computer is. I was surprised to hear it working on my laptop.

If you know that the Mac playback issue has been addressed in a later release of Evolution, please let me know. Otherwise this observation might provide a clue to the developers for resolving the problem.

Reply

• Sep 8, 2024 - 07:52

@RickyChitarrone wrote (parphrased) I might have come across a clue to why this version of Evolution doesn’t play audio. MS3.7 plays fine ... on my old MacBook Pro running OS Mojave. So maybe [the current 3.7 audio device playback glitch is due to] the later OS for Silicon/M1 chip architecture.

Wow. No one else has mentioned that MS3.7 runs on non M1 Macs under Mojave. Thanks for posting.

Hopefully you clue leads to unraveling this major and longstanding stuck point!

Reply

• Sep 14, 2024 - 16:18

I just saw the thread that began on Sept 13. I simply put my info about its working entirely on an older Macbook with OS 10.14.6 (Mojave) where it seemed chronologically latest in this thread. But someplace it branched out, and this information I posted seems not to be part of the discussion. It might be a valuable clue to whoever is in a position to solve it. Where exactly along the line should I repost this info?

Reply

• Dec 28, 2024 - 01:44

Luckily I have an older iMac that runs OS Mojave, the last Mac OS iteration that didn't dismiss 32-bit architecture. I use it for an older version of Sibelius that my M1 Mac won't run. So now I'm using that same computer for MuseScore Evolution. Jojo didn't seem too optimistic about developers rushing in to fix this. Das ist aber etwas eine Schade. Oh well.

Reply

• Jan 1, 2025 - 04:10

Hi @Jojo-Schmitz and @scorster. Now Evolution makes sound on my Silicon Mac.

I downloaded the newest Mac build, 3.7.0.12565751008. It didn't play back either, BUT I found the solution tucked in a different thread after I went chasing geese and netted me a real Wolpertinger! This solution comes courtesy of a 2022 post by @little-island.

  1. Download the zip file from that thread and open it
  2. Rename the one called "libportaudio.2_3.5.0.dylib" to "libportaudio.2.dylib"
  3. Go to Applications, find MuseScore
  4. Right-click the app, choose "Show Package Contents"
  5. Inside there find Contents/Frameworks/libportaudio.2.dylib
  6. Drag the downloaded file into that directory, replacing the file of the same name
  7. Start up MuseScore

The zip file referenced is this, posted by @gabrielwave20 in 2021 in node 320037:

https://musescore.org/sites/musescore.org/files/2021-04/libportaudio_3…

Reply

• Jan 3, 2025 - 04:54

Looking forward to running the latest 3.7 builds on MacOS.

I downloaded and installed the MuseScore 3.7.0.12582252621 Devel.app

I ran the following in the Terminal:

      JBs-mb-5:~ John$ xattr -c/Applications/MuseScore\ 3.7.0.12582252621\ Devel.app

In other words I performed the following three steps to remove the security quarantine:

1) I opened Terminal and pasted the following into the command line

     xattr -c

2) I added the directory path (by simply dragging the app from the Applications folder)

3) I pressed Return

But I got this error message:

     xattr: invalid option -- /

Not surprisingly, when trying to launch the app I still get the “MuseScore 3.7.0.12582252621 Devel.app” is damaged and can’t be opened.

Is there an error in the command line I provided?

Update:

I'm not Unix savvy. Fortunately Jojo stated below that I failed to have a space character after the -c

So then the correct steps, in full are:

1) open the Terminal app and paste in the following command—including the space:

xattr -c

2) drag the app from the Application folder to the prompt line. In my case that results in the following command

 JBs-mb-5:~ John$ xattr -c /Applications/MuseScore\ 3.7.0.12582252621\ Devel.app

3) press return and close the Terminal

If MuseScore 3.7 still reports as damaged, drag an .mscz file onto it. After it opens you're good to go.

Reply

• Jan 3, 2025 - 04:57

UPDATE:  Just moments later.

Ah ... SUCCESS!

I remembered Jojo had also suggested to initially open the app by dragging an .mscz score onto its icon in the MacOS Finder. And THAT WORKED! (Of course one must first dequarantine the app. which I did with the attr x command.)

Now MuseScore Evolution 3.7.0.12582252621 revision: e0df627 opens normally on my M2 MacBook, and it automatically recognized my audio devices!

Thanks to Jojo and everyone who saw this through!!

MacOS users can now use the latest revisions of MS3.7 with playback enabled via their audio devices.

scorster

Reply

• Jan 3, 2025 - 05:22

BTW, I recall that there's a yearly amount to pay Apple for the option to create "signed" versions of MuseScore Evolution 3.7—which would allow the app to run immediately after installation, without the need to enter the Terminal and alter permissions via the command line.

Just want to say that I'd willingly contribute to a fund to cover developer's costs on this matter.

Is that something you'd consider Jojo?

Reply

• Jan 4, 2025 - 23:14

I've now gotten enough funding for an Apple Developer's account for 2 years plus a few months, thanks to 3 very the generous donators! (Not sure whether I'm allowd to pulish their names, so won't, unless/until being given explicit permission, like via the contact form)
I just subscríbed for the 1st year (and deducted 99€ from the PayPal pool (greedy Apple used a 1:1 exchange rate for € to $) and tried to set that up in GitHub.

I've manually triggered one and we're not quite there yet:

Error: HTTP status code: 403. Invalid or inaccessible developer team ID for the provided Apple ID. Ensure the Team ID is correct and that you are a member of that team.
Notarize failed

So something is wrong, not sure what though or how to get a 'developer team ID'

More tomorrow...

Edit: seems I need to wait until that account order gets processed and the account fully activated, may allegedly take up to 48 hours (I suspect though they mean 2 business days)...

Reply

• Jan 3, 2025 - 16:10

Sound has always worked out of the box on pre-Silicone Macs, at least on OS 10.14.6, i.e. the latest iteration of “Mojave”. I never upgraded the OS for my older Maca past that iteration. That disclosure so that it’s clear: I don’t know if the full functionality is because of the older OS or because of the computer’s chipset.

I don’t know what you mean by PR.

Reply

• Jan 3, 2025 - 02:56

It works. Follow the directions. Mine is an M1 and it works fine now. Something about whatever file the instructions had me replace was the problem. It's so nice to hear my work played back at me! I say go for it.

I'd have written to you directly, but I have no idea how to reach outside the forum.

Reply

• Jan 7, 2025 - 23:55

@RickyChitarrone

Yes. All that! AND I'm really grateful for your contribution which brought the various pieces together.

And soon MuseScore Evolution 3.7 should have smooth MascOS installations thanks to developer notarization. Finger crossed on that one.

By the way, I'm seldom impressed with Lute duets but this is truly extraordinary:

     https://www.youtube.com/watch?v=XQsvuKw5-UA

I hope we get high quality MuseSounds lutes and theorbo instruments soon!

scorster

Reply

• Jan 8, 2025 - 05:28

Thanks cadiz1,

Indeed. I've previously enjoyed that very video.

When Birula takes the melody Kowalska lays back quite supportively. But in contrast there's a nuanced temporal detail that leaves me feeling unsettled: Frequently I hear Birula timing parts of his accompaniment slightly ahead of Kowalska's melody, and to me that slightly diminishes the delicate balance of the dance. Nevertheless it's quite a lovely performance and an extraordinary set of compositions by Sylvius Weiss.

Anna Kowalska & Anton Birula are huge contributors.

Thanks for the link!

Reply

• Jan 8, 2025 - 03:22

@RickyChitarrone wrote
> That lute duet is me and my partner! He's the younger, good looking one. I'm the geezer.

Thanks, I was 99% sure that was you. I saw your image on Github and then noticed "Lutenist, Music Director, Teacher" on your Github profile page.

Over the last ten years much of my favorite classical music is from Weiss, Dowland, de Visée, Gottlieb Baron, Zamboni, Kapsberger ... it's such a rich repertoire, and the tone and resonance of many of the instruments is like nothing else!

At some point I hope to contact you by PM. In the meantime, is your theorbo tuning reentrant? Is that the standard?

Reply

• Jan 8, 2025 - 08:45

The stuff you tested earlier was the result or a OR, Pull Request, a proposed code change. Merging that means to accept and integrate it into the main repository, so it is part of all subsequent builds (in this save of the 3.x brand of my fork of the MuseScore 'upstream' repository).
Clear as mud?

Reply

• Jan 8, 2025 - 19:12 
"xattr -r -d com.apple.quarantine /path/to/MuseScore.app"

instead of

"xattr -c /path/to/MuseScore.app" .

The difference between these 2 commands is that the former removes just the quarantine attribute, but recursively (when applied to a directory), while the latter removes all attributes but not recursively, from the target file only.
At least that is what I gather from the manuals (https://ss64.com/mac/xattr.html).

Reply

• Jan 8, 2025 - 22:15

@Jojo This comment is for me(knoike), right?

> At least that is what I gather from the manuals (https://ss64.com/mac/xattr.html).

Thank you for that link information.
Yes, I already knew about the function of the -r option, but I'm just now know about the detail of the the -d and -c options. Thanks.

> -d Delete the given attribute.
> -c CLear all Atrributes.

It seems that both '-d com.apple.quarantine' and '-c' are almost equivalent as the workaround for the issue of notarization.

Now, the notarization(certificate) has been included in '3 Evolution', so this workaround is no longer necessary!
Great work, Jojo!

Reply

• Jan 8, 2025 - 23:05

Sort of for you, but also for myself trying to figure things out

I'm currently having a lot of fun (not!) with that code signing and notarization buisiness, so far I burned 2 days on this...
So no, it is not yet done, still work in progress. Currently I keep getting an error from spctl:
Screenshot 2025-01-09 000213.png
reg. "Unnotarized Developer ID"
and a notarization that takes several hours (I interupted after some 3 hours, now one is running and I'll leave it runing over night)
This is a royal pain!

Reply

• Jan 9, 2025 - 08:44

Well, failing notarization is fine here, better than hanging, as I saw earlier, it is the previous step, the code signing, that goes wrong, doesn't seem to like my developer ID

Reply

• Jan 9, 2025 - 13:49

[attention, getting technical ;-)]

right after the code signing "spctl --assess --type execute "${VOLUME}/${LONGER_NAME}.app"" reports (something like) "${VOLUME}/${LONGER_NAME}..app: rejected", when made more verbose (using "-vvv") it additionally reports "source=Unnotarized Developer ID", which seems nonsensical, as Developer IDs do not get notarized, only apps do, and also this is the step before the actualy notation takes place.

So there's

  1. code signing (seems fine, reporting "replacing existing signature")
  2. spctl (errors, see above)
  3. verifying the code signing (seems fine, reporting "valid on disk" and "satisfies its Designated Requirement")
  4. notarization (fails)

Same order as upstream (see https://github.com/musescore/MuseScore/blob/df9dbe567b8004a4d51edec9532…, for steps 1-3,) and there it works.

Reply

Do you still have an unanswered question? Please log in first to post your question.