AppReviewDebug

LanguageEN中文

Guideline2.1

App Completeness

2.1 is Apple saying the review could not finish. The reviewer hit a wall — login, crash, empty feature, or a binary that does not match the listing — so they stopped.

§ 01What this rejection usually means

  • The review was blocked before anyone judged the product idea.
  • A demo account that fails is the most common trigger, not a missing feature list.
  • Placeholder screens, coming-soon buttons, and TestFlight leftovers read as an unfinished binary.

§ 02Common causes

  • Demo credentials in Review Notes are wrong, expired, or need an extra OTP the reviewer cannot complete.
  • Login is gated by region, invite code, or a third-party account the reviewer does not have.
  • The build crashes on first launch on the review device or OS version.
  • IAP, subscriptions, or paid features are not available in the sandbox.
  • The binary still contains lorem copy, hidden menus, or debug switches.

§ 03How to diagnose your case

  1. Reproduce the exact path in Review Notes on a clean device, signed out, using only the credentials you sent.
  2. If login is the blocker, treat it as a reply-first case until you prove the binary is actually broken.
  3. If the app crashes or a core screen is empty, you need a new build — do not argue the guideline.

§ 05What to inspect in your project

Checklist

  • Review Notes: username, password, and any one-time setup written as a numbered list
  • Sandbox testers and IAP products are Ready to Submit
  • First-launch crash on a factory-reset simulator and a physical device
  • Feature flags default to the production path, not an internal one
  • No hidden debug gestures that change the reviewed experience

§ 06What not to do

Do not

  • Do not resubmit the same build with a one-line “please try again.”
  • Do not hide the login wall and hope the reviewer skips it.
  • Do not put the only working account behind a personal WeChat / Google login you cannot share.

§ 07Questions people ask next

Do I need a new build for Guideline 2.1?
Not always. A bad demo account is often fixed with a reply. A crash, empty feature, or broken IAP usually needs a new binary.
Should I appeal a 2.1 rejection?
Almost never as the first move. 2.1 means review did not finish. Give them a working path first.

Related rejection wording

Related cases