asc-submission-health

Validate and submit iOS/macOS apps to App Store Connect review.

954|51|Updated Jan 27, 2026

Search Tags:#release management #build validation #review process #submission #app store connect #encryption compliance

Ready to run

npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-submission-health-rudrankriyam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: asc-submission-health
Source: https://github.com/rudrankriyam/app-store-connect-cli-skills/tree/main/skills/asc-submission-health
Command: npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-submission-health-rudrankriyam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers proactively identify and fix common issues that lead to App Store submission rejections, ensuring a smoother and faster review process.

Core Features & Use Cases

Pre-submission Checklist: Guides users through essential checks like build status, encryption compliance, content rights, and metadata completeness.
Submission Execution: Facilitates submitting builds for review using either the Review Submissions API or the asc submit command.
Monitoring and Error Resolution: Provides commands to track submission status and offers solutions for frequent rejection errors.
Use Case: Before submitting a new version of your app, run through the pre-submission checklist to catch potential problems like missing privacy policy URLs or incorrect encryption declarations, preventing a delayed review.

Quick Start

Use the asc-submission-health skill to check the status of build ID '1234567890'.

Frequently Asked Questions about asc-submission-health

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate an iOS app build before submitting to the App Store review process?▼

To validate an iOS app build before App Store submission, run a pre-submission checklist covering build status, encryption compliance, content rights, version metadata, localizations, and screenshots to prevent review rejections.

What causes App Store Connect submission errors related to encryption compliance?▼

App Store Connect submission errors related to encryption compliance occur when missing or incorrect encryption declarations are present in the version metadata, which you can identify and fix using a pre-submission validation checklist.

How do I submit a build for App Store review using the Review Submissions API?▼

You can submit a build for App Store review by executing the submission through the Review Submissions API or the asc submit command after completing the pre-submission validation checks.

Can I monitor App Store submission status and resolve rejection errors automatically?▼

You can monitor App Store submission status and resolve frequent rejection errors using dedicated tracking commands that provide guidance for cancellation or resubmission when validation issues arise.

Does asc-submission-health work for macOS applications as well as iOS?▼

Yes, asc-submission-health validates and submits both iOS and macOS applications to the App Store Connect review process, addressing common submission errors across both platforms.

Why does my App Store submission get rejected for missing localizations or metadata?▼

App Store submissions get rejected for missing localizations or incomplete version metadata when pre-submission checks are skipped, making a validation checklist essential to catch these errors beforehand.