The build submitted for review has to be finished and functional — no placeholder text, demo data left visible, dead links, or crashes on the exact device/OS the reviewer tests with.
Why apps actually get flagged
A very common cause is a backend or API endpoint that works in development but is unreachable from the reviewer's network, making core features appear broken.
A real example
"We were unable to review your app as it crashed on launch. Please review the crash logs..."
The short version, in more detail
Guideline 2.1 covers apps that are not ready for review: crashes, placeholder text, broken links, features that do not work, or a review login that does not let the reviewer in. It is also the guideline Apple uses when it needs more information about a new app, particularly from a developer account with little review history. Despite how it sounds, a 2.1 message is often a request, not a judgement of the app.
What this guideline covers
Bugs and crashes found during review on physical devices running the latest operating system.
Placeholder content, unfinished screens and links that do not work.
Access to the app: whether the reviewer can actually reach the features that need an account.
Information Needed requests, where Apple asks for a recording, descriptions and other details before it can complete the review.
Whether in-app purchases referenced in the app are configured and available to the reviewer.
What usually triggers this rejection
The app crashes on launch or during a common flow on a physical device running the latest OS.
Placeholder content, lorem ipsum, "coming soon" screens or links to pages that do not exist.
The reviewer cannot sign in because credentials are missing, expired, or require a code sent to a phone they do not have.
The backend is down, rate-limited or blocks the reviewer's region.
In-app purchases are referenced but not configured or submitted with the build.
For new accounts, Apple asks for extra information about the app and the reply is missing or incomplete.
How reviewers evaluate it
Reviewers install the submitted build on physical devices, not only simulators.
They try the main flows and anything the notes or metadata mention.
If something blocks them, such as a login wall, they usually stop and cite 2.1 rather than guess.
Newer or lower-history accounts are more likely to be asked for additional information.
Common misunderstandings
"Information Needed" does not mean the app was rejected for a defect. It means Apple needs something before it can decide.
It is not only about crashes. A working app can still get a 2.1 if the reviewer cannot get in.
The same guideline number covers very different situations, so the exact message matters more than the number.
Common questions
Why do new developer accounts see 2.1 more often?
Apple appears to ask for more context on submissions from accounts with limited review history, to understand the app before approving it.
Is a 2.1 message always about a bug?
No. It can be about a bug, a missing login, missing information or incomplete features, depending on what the message says.
Does 2.1 affect how my app is rated or ranked?
It affects whether the build is approved. It does not directly change rankings once the app is live.
Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current App Store Review Guidelines for the exact wording.
Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.