Rejection guides / Guideline 2.1: App Completeness (crashes, bugs, placeholders)
Guideline 2.1 - Performance - App Completeness: crashes, bugs and placeholders
This one is a verdict, not a question. The reviewer found the app crashing, broken or unfinished on their device. The good news is it's usually the most fixable rejection there is.
"We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems."App Review Guideline 2.1(a), Apple
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
What the reviewer saw
2.1 App Completeness covers anything that makes the app look unfinished: a crash on launch or on a specific screen, a button that does nothing, a login that fails, a blank screen while a server is down, or placeholder text and images left in the build.
The rejection message usually names the device and OS version the reviewer used, and often attaches a crash log or screenshots. Start there, because the problem is often specific to that device, OS version or network.
Likely causes
- A crash that only happens on the reviewer's device type or OS version, often an iPad when you only tested on iPhone.
- A backend, staging server or API key that works for you but wasn't live, or was rate limited, during review.
- A demo account that expired, was locked, or needs a code sent to your own phone.
- Features that need a permission the reviewer declined, with no fallback when they say no.
- Placeholder content such as "Lorem ipsum", test data, empty screens or links to an unfinished website.
How to fix it
- Symbolicate the attached crash log in Xcode to find the exact line that failed.
- Reproduce on the same device family and OS version the reviewer listed, from a fresh install, signed out.
- Test the exact build you will submit, ideally through TestFlight, against your production backend.
- Check every flow when permissions are denied, when the network is slow, and when the account is new and empty.
- Search the project for placeholder text, test URLs and debug menus before archiving.
- When you resubmit, say in App Review notes what you fixed and how to reach that screen.
Common questions
- The app doesn't crash for me. Why did it crash for the reviewer?
- Usually a difference in conditions: another device or OS version, a fresh install with no cached data, a declined permission, or your server not being reachable from their network. The device and OS in the message are your best clue.
- Do I need a new build to fix a 2.1 App Completeness rejection?
- If the cause was in the app, yes. If it was outside the app, such as a server that was down or a demo account that stopped working, you can fix that and reply in App Store Connect asking them to review again.
- Is this the same as 2.1 Information Needed?
- No. Information Needed means the reviewer paused to ask questions. App Completeness means they found a problem in the app itself.
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
Related guides
- Guideline 2.1: Information Needed
- Guideline 2.1(b): In-app purchases not found or not working
- Checklist: Before you submit to App Review
Apple decides every review. These guides explain what the guidelines say and what usually helps. They can't promise an approval.
Sources: App Review Guidelines (Apple)