Skip to content
Superapp
Esc
navigateopen⌘Jpreview
On this page

App Review and rejections

Understand review statuses, answer Apple clearly, and resubmit with confidence.

A rejection is usually a request for a clearer product, safer behavior, accurate metadata, or better reviewer access. Read the cited guideline and evidence before deciding whether to explain, fix, or appeal.

Give the reviewer a complete path

  • Keep backend services and demo accounts active throughout review.
  • Provide a demo account that does not expire or require a private verification code.
  • Explain non-obvious gestures, hardware requirements, or location-dependent behavior.
  • Describe where subscriptions, account deletion, and restored purchases can be tested.
  • Make contact information accurate so Apple can reach you quickly.

Common preventable rejection reasons

  • Crashes, broken links, unfinished screens, or an incomplete primary journey.
  • The reviewer cannot sign in or reach an important feature.
  • Metadata and screenshots promise behavior missing from the submitted build.
  • The app collects data or requests permissions without a clear, necessary purpose.
  • Account creation exists without in-app account deletion.
  • Digital purchases bypass Apple’s required purchase system.
  • The app provides too little lasting functionality or feels like a thin website wrapper.
  • User-generated content lacks reporting, blocking, moderation, or contact mechanisms.

How to respond

1. Read the complete message

Identify the guideline, the reviewer’s steps, affected device, and whether Apple asks for information or a new binary.

2. Reproduce the issue

Test the same build and account through TestFlight. Do not assume the problem is limited to Apple’s environment.

3. Choose explanation or correction

If the feature already complies, reply with short numbered steps and supporting context. If it does not, fix the app or metadata and state exactly what changed.

4. Reply and resubmit

Use the App Review conversation in App Store Connect. Be factual and respectful; do not create a new app record or submit unchanged builds repeatedly.

Review the current App Review Guidelines before every major release.