App Store rejection reasons and how to avoid them
Apple says over 40 percent of unresolved review issues fall under guideline 2.1, app completeness. The common rejections, the rule behind each, the fix.
By Sohail Hussain21 November 20266 min read
Most App Store rejections are not about breaking a rule on purpose. They are about an app that is not ready: it crashes, shows placeholder content, has a dead link, or the reviewer cannot sign in. Apple says that on average over 40 percent of unresolved issues fall under guideline 2.1, App Completeness. After that come privacy (a missing policy, permission prompts without a clear reason, data declarations that do not match the app, no account deletion), payments for digital content that bypass in-app purchase, social sign-in without an equivalent private option, and apps that are little more than a website. Almost all of them are avoidable with a checklist and a few early design decisions.
Why do most apps get rejected?
Because the reviewer could not use the app as intended. Apple's App Review page lists the usual causes, and the top of the list is guideline 2.1:
- Crashes and bugs on the device the reviewer happens to use, often an iPad running an iPhone-only app in compatibility mode, or the newest iOS version.
- Placeholder content: lorem ipsum, test products, "coming soon" screens, empty states with no data.
- Broken links, including the support and privacy policy links on the listing.
- No working demo account, or a demo account whose backend is down, expired or empty on review day.
The fix is boring and reliable. Test the exact build you submit on several devices, including an iPad if the app runs on one. Fill the demo account with realistic data. Keep the staging and production backends running through the review.
Our mobile app development projects run a pre-submission check against these points before every first release, because a day of checking is cheaper than a week of back-and-forth.
Which guidelines catch the most apps?
As of October 2026, these are the rejections we see most often, with the guideline in Apple's App Store Review Guidelines that each one cites:
| Rejection | Guideline | How to avoid it |
|---|---|---|
| Crash, bug or placeholder content | 2.1 App Completeness | Test the submitted build on several devices; remove every test item |
| Reviewer cannot sign in | 2.1 | Provide a demo account with data; keep the backend up |
| Screenshots or description do not match the app | 2.3 Accurate Metadata | Use real screenshots of this version; describe only what exists |
| No privacy policy, or it is not reachable in the app | 5.1.1 Data Collection | Link the policy on the listing and inside the app |
| Permission prompt without a clear reason | 5.1.1 | Write purpose strings that say exactly why, such as "to scan the QR code on your ticket" |
| No way to delete the account in the app | 5.1.1(v) | Add account deletion in settings, not just a support email |
| Privacy label does not match the app's data use | 5.1 Privacy | Declare every SDK's data collection; check analytics and crash tools |
| Digital content sold through your own checkout | 3.1.1 In-App Purchase | Use in-app purchase for digital goods, or check the storefront rules first |
| Google or Facebook sign-in without an equivalent private option | 4.8 Login Services | Also offer a login, such as Sign in with Apple, that limits data to name and email and lets users hide their email |
| App is a wrapped website | 4.2 Minimum Functionality | Build real app features, or use a mobile website or PWA instead |
| Push used for marketing without consent | 4.5.4 Push Notifications | Ask for explicit opt-in to promotional pushes and offer an opt-out in the app |
| Copy of another app, or many near-identical apps | 4.3 Spam | One app with options, not ten apps from one template |
Which rejections need design decisions, not quick fixes?
Four of the rows above cannot be patched the night before submission. They shape the app, so decide them in the mobile app brief:
Payments. If the app sells digital content, features or subscriptions, Apple requires in-app purchase in most countries, with exceptions for reader apps, person-to-person services and some storefronts. Physical goods and services used outside the app must use your own payment method. The rules have changed several times since 2024 and differ by country; in-app purchases vs web payments explains where the line falls as of October 2026.
Sign-in. Since guideline 4.8 changed in 2024, offering Google or Facebook as the main sign-in means also offering an equivalent option that collects only name and email, lets users keep their email private and does not track them for advertising. Sign in with Apple meets that. Apps that use only their own email and password accounts do not need it.
Account deletion. If users can create an account in the app, they must be able to start deleting it in the app. That needs a backend process for deleting or anonymising their data, which is easier to build at the start than to retrofit.
Minimum functionality. An app that is your website in a frame will struggle under guideline 4.2. If the website is what customers need, a progressive web app may serve them without a store review at all.
What should you do when the app is rejected?
- Read the message and the guideline it cites. Rejections usually quote the guideline and describe what the reviewer saw. Some include a screenshot.
- Decide whether it is a real problem or a misunderstanding. If the reviewer could not find a feature, or misread how payments work, reply in App Store Connect with a short explanation and, if useful, a screen recording.
- Fix and resubmit if it is real. Answer the reviewer's point directly in the review notes, so the next reviewer sees what changed.
- Appeal to the App Review Board only if you are sure the app complies and the reply did not resolve it.
For an app that is already live, Apple's guidelines say bug-fix updates will not be held back over guideline issues except legal ones; you can ship the fix and address the issue in the next version.
How do you check an app before you submit?
Run this list against the exact build and listing you are about to send:
- The build installs and runs on the oldest and newest iOS versions you support, and on an iPad if the app runs there.
- The demo account works, has data, and is in the review notes with instructions for anything unusual.
- No placeholder text, test products or unfinished screens remain.
- Support and privacy policy URLs open, and the policy is also linked inside the app.
- Every permission prompt explains the specific reason in plain words.
- The App Privacy answers cover every SDK in the build.
- Account deletion works from inside the app.
- Digital purchases use in-app purchase, or you have confirmed the exception or storefront rule you rely on.
- Screenshots show this version of the app.
The full submission sequence is in how to publish an app on the App Store, and our app icon generator handles one small thing reviewers do notice: a blurry or mismatched icon.
Does Google Play reject apps for the same reasons?
Google Play's review is driven by policy more than by completeness. The common blocks are a data safety form that does not match the app, missing account deletion on the web as well as in the app, a target API level below the current requirement, and sensitive permissions (SMS, call logs, background location, broad photo access) used without an approved declaration. Crashes matter too, through the pre-launch report and Android vitals. How to publish an app on Google Play walks through each declaration, and the mobile app development guide covers how both store launches fit into the project timeline.
Was this guide useful?