Distributing binaries for macOS outside the App Store requires registering it with Apple beforehand—notarizing it. But do you know what can be submitted for notarization?
Including passwords into the source tree is a big security breach. Similarly including passwords into build jobs would be insecure. Learn how to securely provide Apple ID credentials into notarization jobs.
Distributing macOS apps as ZIP archives has been quaint since Sierra. Today’s macOS packaging requirements mandates notarization, otherwise it would say that your app is suspicious. This often means distributing apps within disk images since this container format can be signed, notarized, and stapled.
Do you distribute your macOS apps as .zip files? That has been quaint since Sierra. You should package your apps as signed and notarized disk images instead. Otherwise Catalina would say that your package is suspicious. However creating disk images is a rather involved process. Read on to find out more.
When your Apple ID is also used for as a publisher for Apple Books or Apple Music, you may hit a snag when trying to notarize your Developer ID application. Here is how to fix it.
Notarizing your app? Make sure you name your bundles correctly beforehand. This includes the main app, extensions, and any sub-bundles inside it.
Notarization requirements is just around the corner in the coming release of macOS. But the Sparkle updater framework is not yet ready for it. Here’s how you can fix that.
macOS Catalina is just around the corner and with it comes mandatory notarization and hardened runtime. If your mac app accepts plugins or otherwise loads 3rd party frameworks and libraries, there are a few caveats that you’ll need to take care.