I have joined the Apple Developer Program and had my plugins signed and notarized. Do I need anything else from Apple to release the AU plugin?
Nope. If you’ve got things signed, notarized (and stapled), you’re good to go.
If you want to distribute in the App Store, whether MacOS or iOS channels, you might have a bit more work to do, such as bundling your .component in an .ipa (for iOS) or creating installers for MacOS.
1 Like
On iOS it needs to be an AUv3 inside an app.
1 Like
Thanks Guys,
This plugin is for distribution outside of the App Store, and it is MacOS only. I had planned to let the user save the plugin to the correct location and not use an installer. If anyone can point me to a good description how to create an installer, I’ll take a look at it. /Thanks
The easy option for installers is to use WhiteBox Packages, which is more or less a “wizard” for the built in macOS dev tools pkgbuild and productbuild.
Unfortunately the Apple documentation for both of those is somewhat obtuse, but a great way to learn by example is the Surge repo, and in the long run it’s worthwhile learning them, especially if you want to do any kind of building on something like GitHub Actions/Azure/etc.
1 Like
Pamplejuce has switched to pkg packaging recently. It is also a great starting point.
1 Like
Great read: How to make macOS installers for JUCE with pkgbuild and productbuild
You can also pkgbuild —expand and see how a few of the big players do things.
2 Likes