When you develop a macOS application and distribute it outside the Mac App Store, users will often see a security warning the first time they try to open it. This happens because Gatekeeper cannot identify the application’s developer, so the app is treated as untrusted.
While there are workarounds to bypass Gatekeeper, they require users to go through multiple manual and advanced steps, resulting in a poor user experience.
As the title suggests, removing this system warning involves two main steps:
To code sign your application, you need to obtain a Developer ID Application certificate from Apple. The process starts by creating a Certificate Signing Request (CSR) using Keychain Access. The CSR proves ownership of a local signing key without exposing the private key itself. Apple uses this request to issue the Developer ID Application certificate.
Before you start, make sure you have:
Your App Name.csr file you created earlier.cer) to your Mac..cer file on your Mac.loginMy CertificatesYou should now see:
🎉 Congratulations! You now have a Developer ID Application certificate ready for code signing.
Notarization is the process where Apple reviews a signed macOS application before it is distributed. The app is submitted to Apple’s notarization service, where it is automatically scanned for malicious content and common security issues. Once approved, macOS can verify that Apple has reviewed the app, allowing Gatekeeper to open it without security warnings.
A new App-Specific Password will be generated. Save it in a safe place.
🎉 Congratulations! Now you should have these information for notarizing your macOS application.