Getting started with SubmitCheck

Understand the local scan, Apple evidence, and hosted submission-report workflow.

Written By Enrique Bonansea

Last updated About 2 hours ago

SubmitCheck helps you find preventable App Store submission problems by comparing your packaged build, App Store Connect evidence, and versioned Apple requirements. It does not guarantee approval or submit your app to Apple.

The three steps

  1. Scan locally: use the SubmitCheck CLI or macOS app to inspect your .ipa or .xcarchive and produce a sanitized JSON manifest. The raw build stays on your Mac.

  2. Connect Apple evidence: use the protected web dashboard to connect App Store Connect and review the evidence available to your account.

  3. Run a check: import the sanitized manifest, preview the exact payload, confirm it is appropriate to upload, and run the submission check.

Start in the dashboard

Open SubmitCheck and choose New check. The page explains the local tools, connection setup, and manifest requirements.

Read coverage with the result

Missing Apple access does not prevent an artifact-only report, but dependent Apple and cross-source rules remain not checked. A successful local scan is not a complete submission review, and a report is not Apple approval.