The App Store submission checklist that actually matches what reviewers check

Metadata and screenshots

Name, subtitle, and description accurately describe what the app does today — not a roadmap feature.

No keyword stuffing in the app name or subtitle; Apple treats this as a metadata violation, not just bad ASO.

Screenshots reflect the real, current UI — no placeholder text, lorem ipsum, or mockups of unshipped features.

Screenshot dimensions match Apple's required sizes for every device class you support.

Privacy

The App Privacy 'nutrition label' in App Store Connect matches what the app and its SDKs actually collect — mismatches are a common rejection and, worse, an App Review Board flag if caught later.

PrivacyInfo.xcprivacy is present with the correct required-reason API codes for any covered API you use (UserDefaults, file timestamps, disk space, etc.).

The privacy policy URL is live, specific to your app, and not a generic template with placeholder company names.

Every permission usage string (camera, location, microphone, etc.) explains the real, specific reason your app needs it.

Account and login

If the app offers any third-party login (Google, Facebook, etc.), it also offers Sign in with Apple with equal prominence.

If the app supports account creation, it also supports account deletion initiated from inside the app, not only by email or web form.

If login is required to use the app, App Review notes include working demo credentials that stay valid until the review completes.

In-app purchases and subscriptions

All in-app purchase products are configured in App Store Connect and attached to the build under review.

Restore Purchases works and is reachable without contacting support.

Subscription length, price, and renewal terms are disclosed near the purchase button, not just buried in a linked page.

No links to external payment pages for digital content or features that must use Apple's In-App Purchase system.

Functionality and completeness

The app launches and runs its core flow without crashing on a clean install.

All test, debug, or placeholder content is removed from the shipping build.

The app offers real utility beyond a single shallow action — reviewers reject thin wrapper or template-feeling apps under Guideline 4.2.

Nothing in the submitted build depends on hardware, region, or an account tier the reviewer can't access.

Reviewer notes

Step-by-step instructions to reach every gated or non-obvious feature, written for someone who has never used the app.

An explanation for anything unusual: hardware requirements, region locks, or features that only activate under specific conditions.