asc-notarization

To notarize a macOS app, you archive it with xcodebuild, export it with a Developer ID certificate, and submit it to Apple's notary service using the asc command-line tool. This workflow prepares your app for secure direct download distribution.

Exporting with Developer ID signing requires validating your signing identities and creating specific export options. The skill configures these steps automatically, ensuring your app bundle is correctly signed for distribution outside the Mac App Store.

Yes, you can staple a notarization ticket to your app or disk image. This attaches the notarization ticket directly to the application, allowing offline validation and ensuring users can run the app without an active network connection.

You can check notarization status and retrieve detailed logs for troubleshooting. The skill provides mechanisms to track the submission progress and fetch logs from Apple's notary service to diagnose any issues during the process.

Yes, you need a Developer ID certificate and App Store Connect access to use this workflow. The process validates your signing identities and submits packages to Apple's notary service, both of which require an active Apple Developer account.

macOS apps need notarization to meet Apple's security requirements for distribution outside the App Store. Notarization verifies the app is free from malicious components, allowing it to run on macOS without triggering Gatekeeper warnings for users.