submit
Submission lifecycle tools; use publish appstore --submit to ship
The submit command is for lower-level App Store submission lifecycle work.
For the canonical high-level App Store publish flow, use asc publish appstore --submit.
Usage
Canonical paths
Use these commands deliberately:asc publish appstore --submit- canonical App Store publish pathasc validate- canonical readiness check before submissionasc submit status- inspect submission or version review stateasc submit cancel- cancel an active submission
submit preflight and submit create compatibility commands
were removed. See Migrate to 1.0 for upgrade mappings.
Submission lifecycle
Validate readiness
Check readiness before you ship:Check status
Inspect a submission by submission ID or version ID:Cancel a submission
Cancel an active review submission:Canonical publish workflow
Ship to the App Store with the canonical high-level publish command:--submit is present.
1.0 migration note
If older automation still invokes the deprecatedasc submit preflight,
migrate it to asc validate. If it still invokes the deprecated asc submit create,
migrate it to asc publish appstore --submit --confirm.
Common errors
No build attached
asc release stage or asc publish appstore to attach the build as
part of the release pipeline.
Missing metadata
asc publish appstore --submit or re-check
with asc validate.
Already in review
asc submit status to inspect the current submission before retrying.
Related
Validate command
Validate before submission
Publish command
Canonical TestFlight publish path
Submission guide
Complete App Store submission workflow