The submit command submits an App Store version for review.
Usage
Submit a version
Submit a version for App Store review:
asc submit --app APP_ID --version VERSION_STRING
asc submit --app 123456789 --version 1.2.0
Always run asc validate before submitting to catch issues early.
Submission process
When you run submit, the CLI:
- Validates the version is ready
- Creates an App Store review submission
- Adds the version to the submission
- Submits for review
Output
✓ Version 1.2.0 submitted for App Store review
Submission ID: submission-id-here
Flags
Version string to submit (e.g., 1.2.0)
Output format: json, table, or markdown
Example workflows
Validate and submit
# Validate first
asc validate --app 123456789 --version 1.2.0
# If validation passes, submit
if [ $? -eq 0 ]; then
asc submit --app 123456789 --version 1.2.0
fi
CI/CD submission
# GitHub Actions
- name: Submit for App Store review
run: |
asc validate --app ${{ secrets.APP_ID }} --version ${{ github.ref_name }}
asc submit --app ${{ secrets.APP_ID }} --version ${{ github.ref_name }}
Check submission status
After submission, check the status:
asc review list --app 123456789
Common errors
No build attached
Error: Version 1.2.0 has no build attached
Solution: Attach a build to the version:
asc versions attach-build --app 123456789 --version 1.2.0 --build BUILD_ID
Error: Missing required metadata for version 1.2.0
Solution: Complete all required fields:
asc app-info set --app 123456789 --version 1.2.0 \
--description "App description" \
--keywords "keyword1,keyword2" \
--whats-new "Bug fixes and improvements"
Already in review
Error: Version 1.2.0 is already in review
You cannot submit a version that’s already in review. Wait for the current review to complete.
Exit codes
| Code | Description |
|---|
0 | Submission successful |
1 | Submission failed |
10-59 | HTTP client errors (4xx) |
60-99 | HTTP server errors (5xx) |
Validate command
Validate before submission
Review command
Manage App Store review details
Submission guide
Complete submission guide