What the message means
Guideline 2.1 sits under Performance. It asks for the final version of the app: all metadata in place, working URLs, no placeholder text or temporary content, tested on a device, and a demo account if the app has a login. Apple says it will reject incomplete app bundles and binaries that crash or show obvious technical problems.
Part (b) covers in-app purchases. Every purchase in the submission has to be complete, up to date, visible to the reviewer and working. If the reviewer cannot find one in the app, Apple asks you to explain why in the review notes.
Common causes
- The app crashed or froze during review. 2.1(a) names binaries that crash or show obvious technical problems.
- The reviewer could not sign in, because the demo account was missing, expired, empty or blocked by a step they could not finish. 2.1(a) asks for demo account info when the app has a login.
- The backend was off or the release build pointed at a server that was down. 2.1(a) reminds you to turn on your back-end service.
- Placeholder content or dead links, such as lorem ipsum, an empty web page behind a button, or a Support or privacy URL that does not load. 2.1(a) asks for fully functional URLs and no temporary content.
- The app used a demo mode without approval. If legal or security obligations stop you from providing a demo account, 2.1(a) allows a built-in demo mode instead, with prior approval from Apple. The mode must show the app's full features.
- An in-app purchase the reviewer could not reach or that failed when they tried it. This is 2.1(b).
Fix it step by step
- Read the whole message in App Store Connect. Write down the screen, the steps and every attachment the reviewer sent.
- Reproduce it on a physical device with a clean install of the same build. If there is a crash log, symbolicate it. Apple links its crash report guides from the App Review page.
- Test the demo account from a signed-out device. Use exactly the username and password in App Review Information. Make sure the account has data and reaches every feature you describe.
- Check the backend. The release build must talk to a server that stays up for the whole review.
- Open every URL in your metadata and inside the app, including Support, privacy policy and terms.
- Walk through every in-app purchase in the submission. If one is not reachable in this build on purpose, say so in the review notes.
- Upload a new build if the code changed, then write review notes that say what changed and where to look.
Reply in Resolution Center
Resolution Center is the App Review section of your app in App Store Connect. Apple's help on replying to App Review messages says you can reply and attach screenshots or documents until you resubmit. Keep the reply short and give the reviewer steps they can follow.
Hello App Review team,
Thank you for the details about Guideline 2.1.
What we found: [the cause in one sentence, e.g. the demo account had expired]
What we changed: [the fix]
It is in build [version (build number)], which we are submitting now.
How to check it:
1. [first step from launch]
2. [next step]
3. [where the fixed feature is]
Demo account: [username] / [password]
Anything else the reviewer needs: [region, hardware, test card, none]
Thank you,
[name]Before you resubmit
- A clean install of this exact build runs on a physical device without crashing.
- The demo account in App Review Information signs in and reaches every feature you list.
- The production backend is up and will stay up during review.
- No placeholder text, empty pages or dead links remain in the app or the metadata.
- Every in-app purchase in the submission is visible and works, or the review notes say why not.
- The review notes say what changed since the rejected build.