// End-to-end release workflows for TestFlight and App Store using asc publish, builds, versions, and submit commands. Use when asked to upload a build, distribute to TestFlight, or submit to App Store.
Track build processing, find latest builds, and clean up old builds with asc. Use when managing build retention or waiting on processing.
Guidance for using the App Store Connect CLI in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.
Resolve App Store Connect IDs (apps, builds, versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.
Sync and validate App Store metadata and localizations with asc, including Fastlane format migration. Use when updating metadata or translations.
Set territory-specific pricing for subscriptions and in-app purchases using purchasing power parity (PPP). Use when adjusting prices by country or implementing localized pricing strategies.
Set up bundle IDs, capabilities, signing certificates, and provisioning profiles with the asc CLI. Use when onboarding a new app or rotating signing assets.
| name | asc-release-flow |
| description | End-to-end release workflows for TestFlight and App Store using asc publish, builds, versions, and submit commands. Use when asked to upload a build, distribute to TestFlight, or submit to App Store. |
Use this skill when you need to get a new build into TestFlight or submit to the App Store.
asc auth login or ASC_* env vars).ASC_APP_ID or pass --app explicitly.asc publish testflight --app <APP_ID> --ipa <PATH> --group <GROUP_ID>[,<GROUP_ID>]--wait, --notify, --platform, --poll-interval, --timeoutasc publish appstore --app <APP_ID> --ipa <PATH> --version <VERSION>--wait, --submit --confirm, --platform, --poll-interval, --timeoutasc builds upload --app <APP_ID> --ipa <PATH>asc builds latest --app <APP_ID> [--version <VERSION>] [--platform <PLATFORM>]asc builds add-groups --build <BUILD_ID> --group <GROUP_ID>[,<GROUP_ID>]asc versions attach-build --version-id <VERSION_ID> --build <BUILD_ID>asc submit create --app <APP_ID> --version <VERSION> --build <BUILD_ID> --confirmasc submit status --id <SUBMISSION_ID> or --version-id <VERSION_ID>asc submit cancel --id <SUBMISSION_ID> --confirmmacOS apps are distributed as .pkg files, not .ipa.
See asc-xcode-build skill for full build/archive/export workflow.
Use xcrun altool (asc doesn't yet support .pkg uploads directly):
# Ensure API key is in ~/.appstoreconnect/private_keys/
xcrun altool --upload-app \
-f "/path/to/YourApp.pkg" \
--type macos \
--apiKey "$ASC_KEY_ID" \
--apiIssuer "$ASC_ISSUER_ID"
Same as iOS, but use --platform MAC_OS:
# Wait for build to process
asc builds list --app <APP_ID> --platform MAC_OS --limit 5
# Attach to version
asc versions attach-build --version-id <VERSION_ID> --build <BUILD_ID>
# Create submission
asc review submissions-create --app <APP_ID> --platform MAC_OS
# Add version item
asc review items-add \
--submission <SUBMISSION_ID> \
--item-type appStoreVersions \
--item-id <VERSION_ID>
# Submit
asc review submissions-submit --id <SUBMISSION_ID> --confirm
Same as iOS flow, use appropriate --platform:
VISION_OSTV_OSWhen releasing the same version across platforms:
Before submitting, verify:
VALID (not processing)See asc-submission-health skill for detailed preflight checks.
--help to verify flags for the exact command.--output table / --output markdown for human-readable output; default is JSON.ITSAppUsesNonExemptEncryption in Info.plist to avoid encryption issues.