asc submission health
Use this skill to reduce review submission failures and monitor status.
Preconditions
- Auth configured and app/version/build IDs resolved.
- Build is processed (not in processing state).
- All required metadata is complete.
Pre-submission Checklist
1. Verify Build Status
asc builds info --build-id "BUILD_ID"
Check:
processingState is VALIDusesNonExemptEncryption - if true, requires encryption declaration
2. Encryption Compliance
If usesNonExemptEncryption: true:
asc encryption declarations exempt-declare --plist "./Info.plist"
asc encryption declarations list --app "APP_ID"
asc encryption declarations create \
--app "APP_ID" \
--app-description "Uses standard HTTPS/TLS" \
--contains-proprietary-cryptography=false \
--contains-third-party-cryptography=true \
--available-on-french-store=true
asc encryption declarations assign-builds \
--id "DECLARATION_ID" \
--build "BUILD_ID"
If the app truly uses only exempt transport encryption, prefer asc encryption declarations exempt-declare --plist "./Info.plist" and rebuild instead of creating a declaration that does not match the binary.
3. Content Rights Declaration
Required for all App Store submissions:
asc apps content-rights view --app "APP_ID"
asc apps content-rights edit --app "APP_ID" --uses-third-party-content=false
Valid values:
DOES_NOT_USE_THIRD_PARTY_CONTENTUSES_THIRD_PARTY_CONTENT
4. Version Metadata
asc versions view --version-id "VERSION_ID" --include-build
asc versions update --version-id "VERSION_ID" --copyright "2026 Your Company"
5. Localizations Complete
asc localizations list --version "VERSION_ID"
6. Screenshots Present
Each locale needs screenshots for the target platform.
7. App Info Localizations (Privacy Policy)
asc apps info list --app "APP_ID"
asc localizations list --app "APP_ID" --type app-info --app-info "APP_INFO_ID"
8. App Privacy readiness advisory
asc can warn about App Privacy readiness, but the public App Store Connect API
cannot verify whether App Privacy is fully published. Before final submission:
asc submit preflight --app "APP_ID" --version "1.2.3" --platform IOS
asc validate --app "APP_ID" --version "1.2.3" --platform IOS
Prefer the version string form for top-level readiness checks in this skill so it stays aligned with asc submit preflight. Lower-level commands later in this guide still use VERSION_ID where the API requires it.
If either command reports an App Privacy advisory, the public API cannot verify
publish state. Use the web-session privacy workflow if you rely on those endpoints:
asc web privacy pull --app "APP_ID" --out "./privacy.json"
asc web privacy plan --app "APP_ID" --file "./privacy.json"
asc web privacy apply --app "APP_ID" --file "./privacy.json"
asc web privacy publish --app "APP_ID" --confirm
If you do not want to use the experimental asc web privacy ... commands,
confirm App Privacy manually in App Store Connect:
https://appstoreconnect.apple.com/apps/APP_ID/appPrivacy
9. Digital goods readiness (IAPs / subscriptions)
If the app sells subscriptions or in-app purchases, validate those separately before submit:
asc validate iap --app "APP_ID" --output table
asc validate subscriptions --app "APP_ID" --output table
In current asc, asc validate subscriptions expands MISSING_METADATA into a per-subscription diagnostics matrix. Use it to identify missing review screenshots, promotional images, pricing or availability coverage gaps, offer readiness, and app/build evidence before retrying submit or first-review attach.
Use --output json --pretty when you want exact territory gaps in machine-readable form.
Submit
Using Review Submissions API (Recommended)
asc review submissions-create --app "APP_ID" --platform IOS
asc review items-add \
--submission "SUBMISSION_ID" \
--item-type appStoreVersions \
--item-id "VERSION_ID"
asc review submissions-submit --id "SUBMISSION_ID" --confirm
Using Submit Command
asc submit preflight --app "APP_ID" --version "1.2.3" --platform IOS
asc submit create --app "APP_ID" --version "1.2.3" --build "BUILD_ID" --confirm
Use --platform when multiple platforms exist.
Monitor
asc submit status --id "SUBMISSION_ID"
asc submit status --version-id "VERSION_ID"
asc review submissions-list --app "APP_ID" --paginate
Cancel / Retry
asc submit cancel --id "SUBMISSION_ID" --confirm
asc review submissions-cancel --id "SUBMISSION_ID" --confirm
Fix issues, then re-submit.
Common Submission Errors
"Version is not in valid state"
Check:
- Build is attached and VALID
- Encryption declaration approved (or exempt)
- Content rights declaration set
- All localizations complete
- Screenshots present for all locales
- App Privacy has been reviewed and published in App Store Connect
"Export compliance must be approved"
The build has usesNonExemptEncryption: true. Either:
- Upload export compliance documentation
- Or rebuild with
ITSAppUsesNonExemptEncryption = NO in Info.plist
"Multiple app infos found"
Use --app-info flag with the correct app info ID:
asc apps info list --app "APP_ID"
Notes
asc submit create uses the new reviewSubmissions API automatically.asc submit preflight can return non-blocking advisories; review them before submitting.- App Privacy publish state is not verifiable via the public API.
- Prefer
asc apps content-rights view/edit over ad-hoc app JSON inspection.
asc validate subscriptions now provides much richer per-subscription diagnostics for MISSING_METADATA cases.- If you use ASC web-session flows,
asc web privacy pull|plan|apply|publish is the CLI path for App Privacy.
- If you avoid the experimental web-session commands, confirm App Privacy manually in App Store Connect.
- Use
--output table when you want human-readable status.
- macOS submissions follow the same process but use
--platform MAC_OS.
