asc-submission-health_skill

Overview

This skill automates preflight checks, submission, and monitoring of App Store review workflows using the asc CLI. It helps reduce submission failures by validating builds and metadata, submitting releases, and tracking review status until completion. Use it when shipping a new version or troubleshooting review problems.

How this skill works

The skill runs preflight inspections against a processed build and your metadata, then uses asc submit create to send a release to App Store review. It provides status and detail commands to monitor submissions and review objects, and supports canceling and retrying submissions after fixes. Human-readable output is available via the --output table flag.

When to use it

• Before shipping a new app version to verify build and metadata readiness
• When automating CI/CD pipelines that produce App Store builds
• To monitor the live review status of a submission or version
• When troubleshooting submission failures and validation errors
• To cancel a problematic submission and retry after fixes

Best practices

• Ensure authentication and app/version/build IDs are configured before running commands
• Confirm the build is fully processed (not in processing state) before submission
• Run metadata validation (asc migrate validate) against your metadata directory
• Use --platform when your app supports multiple platforms to avoid ambiguity
• Use --output table for concise, human-readable status during manual checks

Example use cases

• Run build and metadata preflight checks in CI before calling asc submit create
• Submit a processed build with asc submit create --app APP_ID --version 1.2.3 --build BUILD_ID --confirm
• Poll submission status with asc submit status --id SUBMISSION_ID during review
• List and inspect review objects for more detail via asc review submissions-list and submissions-get
• Cancel a stuck submission with asc submit cancel --id SUBMISSION_ID --confirm, fix issues, then re-submit