Appstore notary runner
Swift-focused AI agent skills for iOS and macOS: build, debug, simulator, SwiftUI, Xcode, App Store workflows. Part of Plug'n Skills.
npx -y skills add Xopoko/build-swift-apps --skill appstore-notary-runnerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Use for the concrete macOS Developer ID notarization command path with xcodebuild export plus `asc notarization` submit, status, log, and stapling. Not for broad packaging readiness review or signing-only diagnosis.
SKILL.md
2.3 KB, as published. Nobody here has run it
App Store Notary Runner
Use for macOS apps distributed outside the App Store with Developer ID signing and Apple notarization.
Use macos-notarization-packager first when the artifact is not clearly distribution-ready. Use macos-signing-inspector for local code-signing, entitlement, Gatekeeper, or trust-policy diagnosis.
Preconditions
- Xcode/CLT configured.
asc auth loginorASC_*.- Developer ID Application certificate in keychain.
- App builds for macOS.
Command Plan Helper
For a deterministic command plan, run the helper from the plugin root:
python3 "$PLUGIN_ROOT/skills/appstore-notary-runner/scripts/notary_plan.py" \
--app-name "YourApp" --scheme "YourMacScheme" \
--archive-path "/tmp/YourApp.xcarchive" \
--export-path "/tmp/YourAppExport" \
--app-path "/tmp/YourAppExport/YourApp.app" \
--zip-path "/tmp/YourAppExport/YourApp.zip" \
--file "/tmp/YourAppExport/YourApp.zip" \
--include-archive --include-export --include-zip --include-submit \
--wait --confirming-actions
The helper prints commands only; it does not build, export, upload, staple, or change trust settings. Commands that write local files or submit to Apple require --confirming-actions. Pass --json for machine-readable output.
Workflow
- Run read-only preflight first: signing identities, trust settings, recent notarization submissions, and existing submission status/log when an ID is known.
- If the artifact is not clearly Developer ID ready, route to
macos-notarization-packagerbefore exporting or submitting. - Archive, export with Developer ID options, verify code-signing authority/timestamp, package as zip/DMG/PKG, then submit.
- Fetch status/log output and repair signed nested binaries, hardened runtime, timestamp, or trust issues before retrying.
- Staple only after Apple accepts the notarization submission.
References
references/appstore-notary-runner.mdfor detailed preflight, archive, export, submit, status, stapling, DMG, PKG, and troubleshooting commands.