In development

See what you can prove about your app before App Review.

StorePreflight reads your project, not your nerves.

A small, local macOS app. It scans a folder with your Xcode project, optionally reads your App Store Connect metadata, and shows what it actually checked, which evidence it found, and what is still unknown.

Free and open source under Apache-2.0. No account on our side, no telemetry. Your sources never leave the Mac.

Twelve narrow checks

Each result carries a status, the Apple source, a next step, and its evidence.

Configuration: permission descriptions, ATS, background modes
Privacy: privacy manifest, ATT and location signals
Flows: sign-in, account deletion, user content, restoring purchases
Metadata: privacy policy, reviewer access

Reads code, runs nothing

SwiftSyntax parses the sources into a syntax tree, so calls in comments and strings are not treated as executable code.

The scanner never builds your project and never runs its scripts or macros. Property lists and privacy manifests are read as files.

App Store Connect, read only

Add your own App Store Connect API key once. StorePreflight performs GET requests only and checks whether the fields you need are present: copyright, build, contact and reviewer access, descriptions, support URL, screenshots, name, privacy policy, category.

The key stays in its own Keychain item. Reviewer credentials never reach a report.

Evidence you can re-check

Every finding points to a relative path with a SHA-256 of the file it came from. Reports export and import as JSON, with your notes and your own manual assessment.

Each project keeps its history, so you can compare runs after a fix.

What a result means - and what it does not

This is a partial assessment, not a prediction. Nothing here forecasts Apple's decision about your app.
Passed covers one described condition in one artifact, for example a non-empty field or valid URL syntax. It says nothing about the quality of the content.
No evidence means unknown, never compliant. A syntactic signal in code asks you for a review instead of deciding for you.
Twelve checks are not full Guidelines coverage. They are a narrow selection with links to Apple's text, including its exceptions.
Known limits: no target or scheme resolution, no xcconfig, no SourceKit symbol identity, no macros, no other languages, no binary or behaviour analysis.

Requirements: macOS 26 or newer, and Xcode 26 or newer with Swift 6.2+ to build it yourself. The interface follows the system language in Polish, English and German.

Questions or a bug? The support page has the details. Data handling is described in the privacy policy, and the rules of use in the terms.