Guideline 2.1 App Completeness: why your app was rejected and how to fix it
Updated
Guideline 2.1 asks for a final, working build. App Review rejects a submission that crashes, shows placeholder content, has broken links, or hides features behind a login the reviewer cannot get past. Part (b) covers in-app purchases that are missing or don't work during review.
Read the full text in Apple’s App Review Guidelines.
Already rejected? Paste Apple’s message and get the fix and a draft reply, free.
The usual causes
The app crashes or hangs during review
Reviewers test on current devices and OS versions, often on a fresh install with no cached data. A crash on first launch, after denying a permission, or on an iPad running your iPhone app is enough for a rejection.
No demo account, or the demo account doesn't work
If your app has a login, App Review needs credentials in the review notes, and your backend has to be running while they test. Expired passwords, accounts that need two-factor codes and staging servers that were switched off are common causes.
Placeholder content and broken links
Lorem ipsum, empty screens, "coming soon" sections, a support URL that 404s or a privacy policy link that goes nowhere all count as an incomplete app.
In-app purchases the reviewer can't find or buy
Every purchase configured in App Store Connect must be visible and working in the build under review. If one can't be reached, say why in the review notes.
Before you resubmit
- Install the exact build on a clean simulator or device and go through every main flow, including first launch and denied permissions.
- Put a working demo account (no two-factor code needed) in the review notes, and keep the backend it talks to running.
- Search the app and the listing for placeholder text, empty states and "coming soon".
- Open every URL in the listing and in the app: support, marketing, privacy policy, terms.
- Make sure every in-app purchase in App Store Connect can be found and bought in this build.
- Launch the iPhone app on an iPad simulator: reviewers do.
How Tapbird checks this
The live run installs your simulator build and uses it like a reviewer: it signs in with the demo account from your review notes, goes through the main flows, records crashes and dead ends, and launches the app on an iPad afterwards. The listing check opens every URL in your store listing.
Apple makes the final decision on every submission. Tapbird is not affiliated with Apple.