Codesigning/Notarization 2024

[Sampletekk]

I've searched the forum and found info about the workflow here, but most of it are a few years old, so just wanted to check if there are any news on this.
I'm developing plugins only, (VST3/AU), and no standalones. I am registered as a Apple Developer.
I do have a background as a software developer, but I have never worked with Codesigning/Notarization before.
Do you need to do both for plugins? What is the difference between them?

[Lindon]

@Sampletekk

read this...

Just a moment...

(www.kvraudio.com)

[Sampletekk]

@Lindon Whohoooo! 28 pages..... In your opinion, is the first post still relevant?

[Lindon]

@Sampletekk said in Codesigning/Notarization 2024:

@Lindon Whohoooo! 28 pages..... In your opinion, is the first post still relevant?

the first post was pretty much updated as we all went along, so it should be a very good guide to what to do..

[ustk]

@Sampletekk Search the Hise forum for codesigning, I reckon @clevername27 made a very detailed tutorial

[ustk]

@Sampletekk found it:

Tutorial: macOS Code Signing, Notorising and Installer (Part II Added)

Introduction This tutorial series will guide you through the complete workflow of building a macOS installer, including code-signing, notarization, configura...

Forum (forum.hise.audio)

[Sampletekk]

@Lindon If I notarize/staple a VST3/AU file, do I need to go through the same process every time I release a new version of the instrument? Given that it's called the same

[orange]

@Sampletekk Yes, everytime you update your software, you need to follow the same instructions

[DanH]

@Sampletekk You only need to codesign your vst3/au files. You codesign & notarize the .pkg installer (and staple if you want). You need to re-codesign each time you export a new version, and re-notarize every new .pkg

[orange]

@DanH As far as I know, notarization is also required for every update. isn't it?

[Lindon]

@orange yep - As far as my workflow goes its codesign and notarise everything every time...

[DanH]

@orange do you notarize your vst3 & au files?

[d.healey]

@DanH said in Codesigning/Notarization 2024:

You only need to codesign your vst3/au files. You codesign & notarize the .pkg installer

This is correct. No need to notarize the individual binaries.

[Sampletekk]

Found this: https://www.youtube.com/watch?v=7bT0gmz0QPw
Does this Notarytool replace the codesign/Notarization process described in the KVR post?

[d.healey]

@Sampletekk said in Codesigning/Notarization 2024:

Does this Notarytool replace the codesign/Notarization process described in the KVR post?

The KVR post was updated to use the notary tool.

[orange]

@DanH said in Codesigning/Notarization 2024:

@orange do you notarize your vst3 & au files?

Since I always distribute plugins with the installer (Whitebox Packages), yes I do.

[d.healey]

@orange You only need to notarize the installer and it applies to the binaries too.

[orange]

@d-healey said in Codesigning/Notarization 2024:

@orange You only need to notarize the installer and it applies to the binaries too.

I already mentioned this above, yes, that's how I do it anyway. In other words, if the installer is being distributed, re-notarization is required with each update.

[d.healey]

@orange oh I read it like you were notarizing your plugins in addition to the installer.

[orange]

@d-healey I think the above statements may cause confusion for some folks.

@Sampletekk In short, (since you will be distributing your products with installer), you need to notarize the installer every time you update the product version.