App Store rejection: The 10 most common reasons and how to fix them
In 2025, Apple rejected about 23% of the 9.1 million submissions it reviewed. The 10 most common rejection reasons, the relevant App Review Guidelines section, and a concrete fix for each.
According to Apple's 2025 Transparency Report, 9,100,620 submissions were reviewed and 2,093,244 were rejected (about 23%). Most rejections come from preventable causes such as crashes, missing demo accounts, mismatched metadata, missing account deletion and sharing data without permission. Each reason maps to a section of the App Review Guidelines; check against this list before you submit.
According to Apple's 2025 App Store Transparency Report, 9,100,620 app submissions were reviewed in 2025 and 2,093,244 were rejected. That is about 23% of submissions. Below are the most common rejection reasons, the App Review Guidelines section behind each one, and how to fix it.
2025 in numbers
| Rejection category (report) | Rejections |
|---|---|
| Performance | 1,354,418 |
| Legal | 495,673 |
| Design | 415,532 |
| Business | 283,820 |
| Safety | 151,159 |
| Other | 4,145 |
According to the report, a submission can be rejected under more than one guideline, which is why the category total is higher than the number of rejections.
Reason → Fix
| Reason | Guideline | Fix |
|---|---|---|
| Crashes, freezes, broken features | 2.1 | Test end to end on real devices and TestFlight |
| Placeholder content | 2.1 | Real copy on every screen |
| No demo account | 2.1 | A working test account in App Review Information |
| Metadata doesn't match the app | 2.3 | Description and screenshots match the app exactly |
| No in-app account deletion | 5.1.1(v) | A working "Delete my account" flow in Settings |
| Data sent to third-party AI without permission | 5.1.2(i) | Clear disclosure and explicit permission before sharing |
| External payment for digital content | 3.1.1 | In-App Purchase for digital content and unlocking features |
| Copycat or indistinguishable app | 4.3 | Explain the difference in review notes and on the store page |
| Non-public APIs | 2.5.1 | Update or replace the library |
| Privacy manifest or old SDK | Upload rule | Privacy manifest with reasons, build with Xcode 26 |
To tick off this list before you submit, use the App Store review checklist tool.
1. Crashes and broken features (2.1)
Section 2.1 (App Completeness) requires submissions to be complete and functional, and apps to be tested on-device for bugs and stability before submission. Performance is also the largest category in the report.
Common sources: heavy work on first launch, empty lists not handled correctly, crashes without internet, a back end that is down during review.
Fix: upload to TestFlight and try it on different devices. Test cases such as airplane mode and slow connections. Walk through the flow the reviewer will see yourself, from start to finish.
2. Placeholder content (2.1)
The same section asks for placeholder text, empty websites and other temporary content to be removed before submission. Text like "Lorem ipsum", "Coming soon" or "Test123" makes the app look unfinished.
Fix: review the text on every screen. Write real copy for empty states too.
3. No demo account (2.1)
Section 2.1 asks apps with a login to include demo account information and to keep the back-end service running.
Fix: in App Store Connect, enter a test account with access to every feature in the App Review Information section. If login uses a one-time code (OTP), explain in the notes how the reviewer can sign in.
4. Metadata doesn't match the app (2.3)
Section 2.3 (Accurate Metadata) requires the description, screenshots and previews to accurately reflect the app's core experience and to be kept up to date with new versions.
Common examples: a screenshot showing a feature the app doesn't have, or an iPad screenshot for an app that only supports iPhone.
Fix: keep your store page exactly aligned with the app; describe real features instead of marketing claims.
5. Missing account deletion (5.1.1(v))
Section 5.1.1(v) requires apps that support account creation to also offer account deletion within the app. Apple has enforced this since June 30, 2022.
Fix: add an easy-to-find "Delete my account" flow in Settings. Users must be able to start the deletion inside the app; "email us" alone is not enough. A confirmation step before deletion is fine.
6. Data sent to third-party AI without permission (5.1.2(i))
Section 5.1.2(i) requires you to clearly disclose where personal data will be shared with third parties, including with third-party AI, and to obtain explicit permission before doing so. Apple added this wording as a clarification on November 13, 2025.
Fix: before the AI feature sends data for the first time, tell users what is sent, to whom and why, and ask for permission. Details are in our post on the AI consent screen.
7. External payment for digital content (3.1.1)
Section 3.1.1 requires In-App Purchase to unlock features or functionality within the app (subscriptions, in-game currencies, premium content and so on).
Fix: use In-App Purchase for digital content and subscriptions. Physical goods and services consumed outside the app don't need In-App Purchase (Section 3.1.3(e)). Read the current guidelines for regional exceptions.
8. Copycat or indistinguishable app (4.3)
Section 4.3 (Spam) rejects multiple Bundle IDs of the same app (4.3(a)) and apps that are indistinguishable from what's already widely available (4.3(b)). In its June 8, 2026 update, Apple clarified the basis for 4.3(a) and 4.3(b) and added examples.
Fix: state concretely in the App Review notes what makes your app different. Offer variants such as cities or teams inside one app instead of separate apps.
9. Non-public APIs (2.5.1)
Section 2.5.1 says apps may only use public APIs and must run on the currently shipping OS. The problem usually comes from an old third-party library.
Fix: update or replace the library.
10. Privacy manifest and old SDKs (upload rules)
These two are not App Review Guidelines sections but App Store Connect upload rules:
- Privacy manifest: according to Apple's documentation, since May 1, 2024, apps that don't describe their use of required reason APIs in their privacy manifest file are not accepted. You can prepare the file with the privacy manifest generator.
- Old SDK: since April 28, 2026, uploads must be built with the 26 SDKs, which means Xcode 26. Details are in our Xcode 26 post.
What to do after a rejection
The rejection message tells you which guideline you hit; read that section first. If something is unclear, you can reply to the review team from the message in App Store Connect.
Fix only the issue that was raised, and list what you changed in the notes when you resubmit. If you'd rather hand the whole store process to us, see our React Native app development service.
Frequently asked questions
How many apps does Apple reject? According to Apple's 2025 Transparency Report, 2,093,244 of 9,100,620 submissions were rejected, about 23%. The largest rejection category was Performance, with 1,354,418.
Can a rejected app be resubmitted? Yes. Fix the issue in the rejection message and resubmit with a new build or updated metadata.
Which guideline covers a missing privacy manifest? It has no section of its own in the App Review Guidelines. It's an App Store Connect upload rule Apple has enforced since May 1, 2024: apps using required reason APIs without a declared reason are not accepted.
Sources
- App Store Transparency Report 2025 (Apple)
- App Review Guidelines (Apple)
- Updated App Review Guidelines now available (Apple, November 13, 2025)
- Updated Apple Developer Program License Agreement and App Review Guidelines now available (Apple, June 8, 2026)
- Account deletion requirement starts June 30 (Apple)
- Describing use of required reason API (Apple)
- Upcoming SDK minimum requirements (Apple, February 3, 2026)