validate
Validate App Store version readiness before submission
The validate command performs preflight validation to check if an App Store version is ready for submission.
Usage
Validate a version
Check if a version is ready for submission:
asc validate --app APP_ID --version VERSION_STRING
asc validate --app 123456789 --version 1.2.0
What it checks
The validation process checks:
- Version has a build attached
- Required metadata is complete (description, keywords, screenshots)
- Privacy policy URL is set (if required)
- Age rating is configured
- App categories are assigned
- Pricing and availability are configured
Output
Success:
Version 1.2.0 is ready for submission
Validation failed for version 1.2.0:
- No build attached to version
- Missing screenshots for iPhone 6.5"
- Description is empty for en-US
Flags
Version string to validate (e.g., 1.2.0)
Output format: json, table, or markdown
Example workflows
Validate before the release pipeline
# Validate version
if asc validate --app 123456789 --version 1.2.0; then
echo "Version is ready, running the release pipeline..."
asc publish appstore --app 123456789 --ipa ./build/MyApp.ipa --version 1.2.0 --submit --confirm
else
echo "Validation failed, fix issues before publishing"
exit 1
fi
CI/CD validation
# GitHub Actions
- name: Validate version
run: |
asc validate --app ${{ secrets.APP_ID }} --version ${{ github.ref_name }}
if [ $? -ne 0 ]; then
echo "Validation failed"
exit 1
fi
- name: Publish to App Store
run: asc publish appstore --app ${{ secrets.APP_ID }} --ipa ./build/MyApp.ipa --version ${{ github.ref_name }} --submit --confirm
Exit codes
| Code | Description |
|---|
0 | Validation passed |
1 | Validation failed |
10-59 | HTTP client errors (4xx) |
60-99 | HTTP server errors (5xx) |
Always run validate before asc publish appstore --submit, or after asc release stage, to catch issues early and avoid rejected submissions.
Submit command
Submit for App Store review
Submission guide
Complete submission guide