Pre-flight

Clear for departure.

Pre-flight runs before every submission. It reads your compiled build, finds what would hold it at the gate in App Store or Google Play review, and points to the file, symbol or setting to change, so your build is clear for departure.

Pre-flight sees what is inside your build. Your store listing, screenshots and business model are outside it, and no tool can promise approval.

01

What it inspects

Three kinds of evidence reviewers act on.

Privacy declarations

Permission purpose strings, matched against the frameworks the binary actually links
Privacy manifests and the reasons declared for sensitive APIs
Third-party SDKs that need their own manifest or signature
Tracking SDKs and domains, and the tracking-permission prompt
Data your Play Data safety form has to account for

Platform rules

Third-party sign-in without Sign in with Apple
References to non-public Apple APIs
Payment SDKs where in-app purchase may be required, flagged for your judgement
Account creation without in-app deletion, flagged for your judgement
Web wrappers that load a remote site instead of shipping an app

Build requirements

Target API level against Google Play's current minimum
Restricted permissions and the declarations they trigger
16 KB memory-page support in native libraries
Foreground-service types, photo and video access
Debug builds, test builds and debug signing

02

Departures

Every check names the rule it protects.

A finding cites the store rule or upload error it would trigger, so you can read the source yourself.

Check	Store	Rule or error
Purpose strings	App Store	ITMS-90683
Required-reason APIs	App Store	ITMS-91053
Privacy manifest structure	App Store	ITMS-91056
SDK manifests and signatures	App Store	ITMS-91061
Tracking transparency	App Store	Guideline 5.1.2
Sign in with Apple	App Store	Guideline 4.8
Non-public APIs	App Store	Guideline 2.5.1
In-app purchase	App Store	Guideline 3.1.1
Account deletion	App Store	Guideline 5.1.1(v)
Minimum functionality	App Store	Guideline 4.2
Target API level	Google Play	Target API requirement
Restricted permissions	Google Play	Permissions policy
16 KB page size	Google Play	Page-size requirement
Data safety coverage	Google Play	User Data policy

03

After a review

From the reviewer's note back to your build.

Trace the cause

Reviewer notes cite a guideline or an error code. APPCHK maps that reference to the Pre-flight check behind it, runs the check on your build, and shows the evidence. You fix the cause, not a guess, for App Store and Google Play alike, offline in the CLI.

Prove the fix

Re-run Pre-flight on the corrected build before resubmitting. The report lists what changed since the rejected build, which is also the clearest answer to give the reviewer.

04

Gate status · APPCHK Cloud

Know when your build boards.

Connect App Store Connect and Google Play to get alerts as a build moves from waiting to in review to released or rejected. From the CLI, the same status check runs with your own key, which never leaves your machine.

05

Early access

Submit once.

Request access Everything APPCHK checks