asc-submission-health

Preflight checks for an App Store submission validate build status, encryption declarations, content rights, version metadata, localizations, screenshots, and privacy policy URLs to prevent common rejection failures before submitting builds for review.

App Store submission failures are commonly caused by missing encryption declarations, incomplete version metadata, invalid privacy policy URLs, or unverified build statuses. You can check for them by running automated preflight checks before submitting your build for review.

Automate App Store build submissions using the asc command-line tool by validating preflight requirements and submitting builds for review via the Review Submissions API or the asc submit command, reducing manual effort and shipping frustration.

Yes, you can monitor App Store review status and handle submission errors using this Skill, which tracks submission progress and provides error details for troubleshooting common failures during the app review process.

Yes, you need specific build IDs and app IDs to validate your App Store submission, as the Skill requires these identifiers to target the exact build and verify its metadata, localizations, and compliance before submitting for review.