JetRise IT Solutions › App development › Rejection fixes › Apple App Store
Fixing an App Store rejection under Guideline 2.1 (App Completeness)
Guideline 2.1 means App Review couldn't fully test your app. It crashed, it needed a login they didn't have, the server wasn't running, something was still placeholder, or an in-app purchase couldn't be found. Most of these are fixed with a new build or better review notes.
What the rule says
- Submit a final version: complete metadata, working URLs, and no placeholder text, empty web pages or temporary content.
- Test on a real device first. Crashes and obvious bugs are rejected.
- If the app has a login, give App Review a working demo account and make sure your backend is live during review. If a demo account isn't possible, a built-in demo mode that shows the full app may be accepted.
- In-app purchases must be complete, visible to the reviewer and working. If they can't be found, explain where in the review notes.
It happened to us too
We submit updates for our own 19 apps every week, so we keep a pre-submission checklist: real-device test on the reviewer's device type (often an iPad), demo login in the review notes, server checked the day of submission, and in-app purchases tested in sandbox.
How to fix it
- Find what the reviewer hit. Read the App Review message and any attached screenshots or crash logs. Note the device (for example iPad Air) and iOS version they used.
- Reproduce it on that device. Test the same flow on that device type. Many 2.1 crashes only happen on iPad, a newer iOS version or a first launch with no data.
- Fix the login path. Add a working demo account (username and password) in App Review Information, and make sure it never expires. Keep your server up during review.
- Make purchases findable. Submit in-app purchases with the version, test them in sandbox, and say in the notes where the paywall is (for example “Settings › Upgrade”).
- Remove placeholders. Check for “Lorem ipsum”, test data, “coming soon” screens, broken links and empty support or privacy pages.
- Upload a new build and reply. Bump the build number, upload, attach it to the version, and add a short note explaining what you fixed.
Questions
Do I always need a new build for 2.1?
If the app crashed or showed placeholder content, yes. If the reviewer just couldn't log in or find a purchase, fixing the review notes or demo account may be enough. Reply in App Store Connect and resubmit.
The app works fine for me. Why did it crash for Apple?
Reviewers often use a different device (frequently an iPad), a newer iOS version, a fresh install or a different network. Test those exact conditions.
Can I use my own account as the demo account?
Use a dedicated test account with sample data, not a real customer's data, and make sure it won't be locked by two-factor prompts.
How long until Apple reviews it again?
Resubmissions usually go back into the queue like any update; most are reviewed within a few days.
Other rejection fixes
- Fixing an App Store rejection under Guideline 2.3.7 (Accurate Metadata)
- Fixing a Google Play Metadata policy rejection for ranking or award claims
Updated October 28, 2026. Store rules change; always read the current message in App Store Connect or Play Console. This page isn't affiliated with Apple or Google.
Stuck on a rejection? We'll fix it.
From $300 for most store rejections, fixed quote first. We deal with Apple and Google review every week for our own 19 apps.