Guideline explainers

App Completeness: what Apple expects before review

Guideline 2.1 is usually about missing information, incomplete flows, hidden purchases, demo account problems, or features that reviewers cannot access. The fix is often operational: give Apple a clear path to test the app.

Developers who received an Information Needed or App Completeness rejection. Guideline 2.1

Common triggers

Reviewers cannot find an in-app purchase, subscription screen, gated feature, or required content.

The app requires a login, special account, QR code, hardware device, location, or business approval without clear test instructions.

The binary, metadata, screenshots, or App Store Connect configuration appears unfinished.

Fix checklist

Add detailed review notes in App Store Connect with step-by-step test instructions.

Provide demo credentials and explain where reviewers can find paid or restricted features.

Remove unused IAP products or metadata claims that are not visible in the submitted build.

Reviewer reply angle

Do not argue that the app works in general. Tell Apple exactly what changed, where to tap, and how to reproduce the reviewed flow.

If nothing changed because Apple missed something, reply with concise navigation steps and evidence.

Generate reviewer notes for Guideline 2.1

AcceptMyApp can turn your app context into review notes, demo instructions, and a safer Resolution Center reply.

Get started