Apple App Review approves or rejects your first submission on a small number of highly specific checks. Most rejections are one round of edits away from approval. This is the list.
The name, subtitle, description, screenshots, and preview video must all describe the app you actually built. If the screenshots show features that are behind a paywall, the paywall must be reachable. If the description mentions integrations, the integrations must work. Guideline 2.3.
The App Privacy label declares what data your app collects. PrivacyInfo.xcprivacy declares which required-reason APIs you use. Both must be accurate; both must match. AI-built apps almost always miss one — the AI does not know what your third-party SDKs collect.
If you offer a subscription, you must offer restore purchases. If you offer any paid feature, it must be through in-app purchase (Guideline 3.1.1). Digital goods only — no external payment for digital goods. Physical goods can use external payment.
If you offer any third-party sign-in (Google, Facebook, X, GitHub) you must also offer Sign in with Apple. Guideline 4.8. AI-generated apps often add Google Sign-In and forget Apple.
Guideline 5.1.1(v) requires an in-app path to delete the account and associated data. A "contact us to delete" email is not sufficient. Apple reviewers test this — build the flow, do not just document it.
A working URL where a user can get help. Apple checks this — a 404 is a rejection.
The questionnaire in App Store Connect must match what the app actually contains. Overstating or understating triggers a manual review.
A demo account with credentials if the app is behind login. Any region-specific features. Any hardware requirements. Anything a reviewer would not discover in the first 60 seconds.
Official documentation this page is grounded in. Verified to resolve.