Codesigning/Notarization 2024
-
There are three processes here, (I think): Notarization, Codesigning and Stapling.
With the Notary tool, as I understand it, you don't need codesigning anymore, correct?
Also, as I understand, Notarization is when you make it so that Macs gatekeeper doesn't throw a warning that the application comes from an unauthorized developer.
What does "staple" and "codesigning (if it's still needed)" do? -
@Sampletekk said in Codesigning/Notarization 2024:
With the Notary tool, as I understand it, you don't need codesigning anymore, correct?
You codesign your plugins/apps.
You codesign and notarize your installer - stapling is part of the notarization process -
@Sampletekk said in Codesigning/Notarization 2024:
What does "staple" and "codesigning (if it's still needed)" do?
Plugins and installers containing plugins must be codesigned. Staple is the process performed after notarization.
So you have to follow the steps below if you want to distribute plugins for macOS:
Export your plugin with HISE --> Codesign plugin --> Create an installer app --> Codesign the installer app --> Notarize the installer app --> Staple the installer app
Then your plugins will be able to run on DAWs on macOS without any Gatekeeper issues.
-
@Sampletekk Are you still having issues?
-
I know this may muddy the waters a bit...but ive actually never code signed my VST3/AU...only my AAX because its required...Ive only ever codesigned the .PKG when I was using those and the Standalone app(via apple's signing/ notarizing in Xcode) now I have a custom installer that I built and I only have to codesign/Notirize it via Xcode(not via the terminal) and I dont worry about the cosigning any of the individual binaries...and all my plugins run just fine for my users...