Submitting for review (and passing)
Complete your store listing, submit, and understand what reviewers look for so you pass on the first try.
Final step: the public App Store listing and review. A human (aided by automated checks) will evaluate your app against Apple's guidelines. Most first-time rejections are avoidable and specific — Apple tells you exactly what to fix.
Complete the store listing
- 1Screenshots — capture them from the simulator (⌘S saves a screenshot) for the required device sizes. Show your real screens.
- 2Description, keywords, category — write a clear description; a model can draft it from your SPEC.md. Category: e.g. Lifestyle or Productivity.
- 3Privacy policy URL and the App Privacy answers from Module 7.
- 4Support URL — even a simple contact page counts.
- 5Select the build you tested in TestFlight and click Add for Review ▸ Submit.
What reviewers most often reject
- Crashes or bugs on their device — your Module 6 hardening and TestFlight testing directly prevent this.
- Inaccurate privacy declarations — make sure App Privacy matches the AI network call.
- Placeholder or broken content — no lorem ipsum, no dead buttons, no 'coming soon' screens.
- Misleading metadata — the description must match what the app does.
Rejections come with a specific reason in the Resolution Center. Read it literally, fix that exact thing, reply or upload a new build, and resubmit. Most indie apps that ship were rejected at least once. It's a checklist step, not a verdict.
Review typically takes anywhere from a few hours to a couple of days. Once approved, you choose to release immediately or on a date — and your app is live on the App Store, downloadable by anyone in the world.