Check your submission before App Review.

Your iOS or iPadOS build. Your App Store Connect configuration. Apple’s requirements. SubmitCheck is being built to check them together and reveal mismatches, missing evidence, and what needs attention.

Part of emonster’s developer tools, SubmitCheck combines local build inspection with a separate web portal for evidence-based submission checks. Join the waitlist for launch news.

Your binary stays on your Mac. Your Apple API key is encrypted in server-side Secret Manager.

Join the waitlist
Inspect your exact build

The macOS app and CLI inspect .ipa and .xcarchive files offline. Review sanitized JSON before sharing; raw builds stay on your Mac.

Spot submission mismatches

The protected web portal compares build and Apple evidence—for example, local build 42 versus selected build 41. It never edits or submits to App Store Connect.

Understand every finding

Findings link evidence to versioned Apple requirements and fixes. Missing evidence is never a pass; AI guidance is separate. Apple decides approval.

Choose the way you ship.

Planned pricing for hosted reports. Local inspection and JSON export do not require a hosted purchase. Joining the waitlist does not purchase a plan. All prices are in USD.

Monthly

For recurring release work.

$19.99billed monthly

  • Up to 10 new submission cycles per monthly allowance window
  • Up to 110 successful hosted reports per allowance window
  • 1 bundle ID per cycle
  • 7 days per cycle from its first successful report
  • 1 initial report plus up to 10 successful rescans per cycle
  • Allowance refreshes monthly
  • Unused capacity does not roll over
  • Evidence, source links, and remediation in every report
  • Failed jobs and duplicate payloads do not consume reports
  • No automatic overage charges

Annual

For year-round release work.

$169.99billed annually

  • Up to 10 new submission cycles per monthly allowance window
  • Up to 110 successful hosted reports per allowance window
  • 1 bundle ID per cycle
  • 7 days per cycle from its first successful report
  • 1 initial report plus up to 10 successful rescans per cycle
  • Allowance refreshes monthly
  • Unused capacity does not roll over
  • Evidence, source links, and remediation in every report
  • Failed jobs and duplicate payloads do not consume reports
  • No automatic overage charges