App Store Guideline 2.1 App Completeness: How to Pass
Updated: October 2026
Guideline 2.1 (App Completeness) means the app you submit to Apple must be a finished, working version, tested on a device, with no crashes, placeholder content or broken features. It is one of the most common reasons iOS apps are rejected, and also one of the easiest to prevent.
What does Guideline 2.1 say?
In simple words, Apple expects that:
- Your submission is the final version, with all required metadata and working URLs.
- Placeholder text, empty websites and other temporary content are removed.
- The app was tested on a device for bugs and stability before you submit.
- If the app has a login, you provide demo account details and your backend service is turned on.
- If the app has in-app purchases, they are complete and visible to the reviewer, or you explain in the review notes why they are not.
Always read the current wording in Apple’s App Review Guidelines, because Apple updates them.
What usually triggers a 2.1 rejection?
- A crash on launch or during a main flow. The reviewer opens the app and it closes.
- A button or feature that does nothing.
- A login the reviewer cannot pass, because no demo account was provided or the account does not work.
- A backend that is offline, so screens stay empty or show errors.
- Placeholder content, such as “lorem ipsum” text or test images.
- Dead links, such as a support page or privacy policy that does not open.
- In-app purchases that fail or cannot be found by the reviewer.
- Features that need hardware or data the reviewer does not have, with no explanation in the notes.
Checklist: pass Guideline 2.1
- Install the final build on a real iPhone and use it for at least a full session.
- Tap every screen, button and menu item.
- Test first launch after a fresh install.
- Create a demo account and test it from a clean device. Write it in the App Store Connect review notes.
- Confirm your server is live and will stay live during review.
- Replace all placeholder text and images.
- Open every link in your app and your metadata.
- Test in-app purchases from start to finish.
- Test with permissions denied and with no internet connection.
- Write clear review notes for anything the reviewer might not understand.
Why testing on a real device matters here
The guideline says on-device. A Simulator cannot show real memory limits, camera behavior, cellular connections or touch input. A bug that only appears on an iPhone is exactly the kind a reviewer will find, because the reviewer uses real devices.
What if you were already rejected under 2.1?
- Read the reviewer’s message and note the exact problem.
- Reproduce it on a real iPhone.
- Fix it, then test the whole app again, not only that screen.
- Reply in Resolution Center if needed, and resubmit.
Fixing one bug and breaking another is common, so a full re-test before resubmitting saves you a second rejection.
Frequently asked questions
Is Guideline 2.1 only about crashes?
No. It also covers incomplete content, broken links, missing demo accounts and unfinished features.
Do I need a demo account?
Yes, if your app has a login. Without it, the reviewer cannot see your app.
How can I check my app before submitting?
Test it yourself on a real iPhone, and consider a tester who has never seen it. RealAppTest does this by hand and sends you a report.