HOWTO macOS notarization (plugins, app, pkg installers)

[Lind0n]

Did you try this?

1. Sign App
2. Notarize App
3. Staple App
4. Zip App

its a plugin not an app. If you read the early instructions on this page it suggest plugins will need to be zipped to Notarize...more than happy to be told this is no longer required.

[newsonicarts]

So I see apple have created more ways to collectively waste all our time as we are now forced to move to notarytool from altool

Has anyone yet tried this? is it a drop in replacement for altool (i guess not, its never that easy with apple) if so any hints on what needs changing?

[audiothing]

So I see apple have created more ways to collectively waste all our time as we are now forced to move to notarytool from altool

Has anyone yet tried this? is it a drop in replacement for altool (i guess not, its never that easy with apple) if so any hints on what needs changing?

It’s actually much easier now, you don’t need to create your own loop to wait for the notarization to finish.

[discoDSP]

I think notarytool isn't required until next 2023 fall but will update the main thread once there's enough info to document how to use it.

[newsonicarts]

So I see apple have created more ways to collectively waste all our time as we are now forced to move to notarytool from altool

Has anyone yet tried this? is it a drop in replacement for altool (i guess not, its never that easy with apple) if so any hints on what needs changing?

It’s actually much easier now, you don’t need to create your own loop to wait for the notarization to finish.

Good to know, but are the command line parameters the same or have changed much?

[newsonicarts]

I think notarytool isn't required until next 2023 fall but will update the main thread once there's enough info to document how to use it.

Ah ok, thats also good to know. I did see a date flash up but it didn't sink in it to my brain it was almost a year off.

[Markus Krause]

I am currently using BigSur for my builds, but I am using another old Mac with MacOS10.14 for notarisation. This way i am able to be still downward compatible to MacOS 10.12 while supporting the M1.
I assume downward compatibility will break (again...) as soon as we are forced to use notarytool?

---

Further observations that I rencently made:
Make sure that you do not use aliases in your .component or .vst files (the Steinberg VST3 SDK does this). This does not pass notarisation.

[audiothing]

Good to know, but are the command line parameters the same or have changed much?

It's just two commands now:

Code: Select all

xcrun notarytool submit $YOURFILE --keychain-profile "AC_PASSWORD" --wait
xcrun stapler staple $YOURFILE

We save the output of the firt command to a file, then check the status, if it's "Accepted", we run the stapler.

You can also add a webhook and compared to the old method it seems the upload is much faster. Check this:
https://developer.apple.com/documentati ... n_workflow

[audiothing]

I am currently using BigSur for my builds, but I am using another old Mac with MacOS10.14 for notarisation. This way i am able to be still downward compatible to MacOS 10.12 while supporting the M1.
I assume downward compatibility will break (again...) as soon as we are forced to use notarytool?

Once again, you don't need an older macOS to support older macOS/OS X versions. We support down to OS X 10.9 and we build and notarize everything on one machine with macOS Monterey (12.3.1). You are just making everything unnecessarily complex.
No, downward compatibility is still the same with notarytool.

[quikquak]

I've just upgraded to Ventura and you can only install Xcode 14 - which gives warnings about targeting earlier MacOS versions.
And someone has reported that forcing targeting on Xcode 14, to earlier OS produces errors for the latest OS.
So I can’t target to old MacOS at all, and I can’t install Xcode 13 on Ventura. DOH!

I guess I'm only targeting for the latest now.

[audiothing]

I've just upgraded to Ventura and you can only install Xcode 14 - which gives warnings about targeting earlier MacOS versions.
And someone has reported that forcing targeting on Xcode 14, to earlier OS produces errors for the latest OS.
So I can’t target to old MacOS at all, and I can’t install Xcode 13 on Ventura. DOH!

I guess I'm only targeting for the latest now.

Can you downgrade to Monterey? That should be safe to use at least for another year. Then it's time to drop 10.9 for good

[quikquak]

Good grief Apple!
With 14.1, MacOs 10.13 was the earliest I could compile for!
I can't believe I have to install another operating system just to support customers! My Mac is getting dangerously close to going out the window... again.

[quikquak]

*sigh* I think I'm going to go with Apple's flow, and only target High Sierra onwards.
Passing Apple's fuckduggery straight down to the customer, which is what they want me to do, right?

[mystran]

Good grief Apple!
With 14.1, MacOs 10.13 was the earliest I could compile for!
I can't believe I have to install another operating system just to support customers! My Mac is getting dangerously close to going out the window... again.

Does this hold for the xcode command line tools as well?

[quikquak]

Good grief Apple!
With 14.1, MacOs 10.13 was the earliest I could compile for!
I can't believe I have to install another operating system just to support customers! My Mac is getting dangerously close to going out the window... again.

Does this hold for the xcode command line tools as well?

I don’t believe so. I’ve heard you can also run Xcode 13 from the terminal, so their barrier seems to be just cosmetic.