Help › Guideline 2.1 – App Completeness / Information Needed

Guideline 2.1 App Completeness rejection: how to find and fix the bug

Updated [DATE] · Plain-English guide, not official Apple or Google text.

Quick answer: The reviewer hit a crash, an error, a blank screen or a login problem, or they need something (a demo account, a demo video, hardware) to finish the review. The 'Bug description' and 'Review device details' lines tell you where to look.

What the rejection looks like

“The app exhibited one or more bugs that would negatively impact users. Bug description: The app displayed a blank screen after the reviewer signed in with the provided demo account, preventing them from continuing.”

Real example shared publicly: source. Exact wording varies.

Common causes

Crash or blank screen on the reviewer's device (often iPad or IPv6 network)
Backend was down or returned nothing during review
No working demo account, or it needs SMS/2FA
In-app purchase products not loading (wrong product ID / not submitted)
Feature needs hardware or a QR code the reviewer doesn't have, so they ask for a demo video

How to fix it

Read the 'Bug description' and 'Review device details' lines: note the device (often an iPad) and OS version
Reproduce on that device type with a clean install (delete the app first) and with an update install
Test with no network, a weak network and an IPv6-only network (macOS Internet Sharing has a NAT64 option)
Check every permission-denied path (camera, location, photos) shows a usable screen, not a dead end
Confirm your backend, API keys and feature flags are live in production during review
Check that in-app purchase products load (product IDs match App Store Connect and the products were submitted)
Make sure the demo account works, has data, and needs no SMS/2FA code; if needed provide a demo mode
If Apple asked for a demo video: record the current build on a physical device showing every feature and permission prompt (and any hardware)

Decode your exact message

Paste your full rejection into the free decoder to confirm the guideline and see the likely causes. It runs in your browser; nothing is uploaded.

Decode my rejection free

Want the reply written for you?

The $9 Fix Pack (coming soon) adds a reviewer reply template, a resubmission checklist and ready prompts for your coding tool for this guideline.

See the Fix Pack

FAQ

It works on my phone. Why did it fail?

Reviewers often test on an iPad, with a clean install, on an IPv6 network, and sometimes deny permissions. Reproduce under those conditions.

Do I always need a new build?

For bugs, yes. For 'Information Needed' (e.g. a demo account or video), replying with the information is often enough.

Official source: https://developer.apple.com/app-store/review/guidelines/#app-completeness

Apple and Google decide every review. This guide is general information, not legal advice, and can't guarantee approval.