asc-notarization

To notarize a macOS app for distribution outside the App Store, you archive the project with xcodebuild, sign it with a Developer ID Application certificate, and submit it to Apple using asc notarization. The process handles submission status checks automatically.

For Apple notarization using xcodebuild, you need an Xcode project and a Developer ID Application certificate. The Skill guides you through archiving the app, signing it, and managing App Store Connect authentication for submission.

App notarization with Developer ID signing works by archiving your macOS application, applying the Developer ID certificate with codesign, and submitting the archive to Apple. The system then checks the submission status until approval is received.

Yes, you can staple the notarization ticket to your macOS app for offline use. The Skill provides optional ticket stapling, which applies Apple's ticket directly to the app, allowing it to function without a live connection to Apple's servers.

macOS app notarization requires App Store Connect authentication to securely verify your developer identity when submitting the application. The Skill focuses on managing this authentication alongside Apple's strict notarization requirements for Developer ID certificates.

The best way to submit a macOS app for Apple notarization is to use the asc notarization submit command with your packaged application file. This initiates the submission, handles status checks, and supports optional offline stapling.