iOS & Android Published with Cloudy

DataApp Review

Why Apple rejects apps: the 2025 App Review numbers

Apple publishes how many apps it turns away and why. We went through the last three reports to see where apps really fail, and what to fix before you press Submit.

Published Updated 8 min read
Illustration of a phone on a desk next to a stack of submission forms, the top one marked with a red stamp, a pencil and a cup of coffee
On this pageThe 2025 numbers
  1. The 2025 numbers
  2. Three years compared
  3. What each section covers
  4. Apple's most common rejections
  5. What we check first
  6. What the report can't tell you
  7. Questions people ask
  8. Related reading

The short answer

Apple reviewed 9,100,620 app submissions in 2025 and rejected 2,093,244 of them. That's about 23 in every 100. The Performance section of the rules, home of crashes and half-finished apps, was cited 1,354,418 times, more than the other five sections combined. Apple says over 40% of unresolved issues come from one rule, guideline 2.1, App Completeness.

Apple turned away 2.09 million submissions in 2025

Every year Apple puts out an App Store Transparency Report. The 2025 report says App Review looked at 9,100,620 submissions and rejected 2,093,244. Mind the word submissions. Send the same app in three times and Apple counts three.

The report also splits rejections across the five sections of the App Review Guidelines, plus a small "Other" pile.

Rejections by section of the rules, 2025

How many rejections cited each section

  1. PerformanceSection 2. Crashes, unfinished apps, wrong metadata1,354,418
  2. LegalSection 5. Privacy, data, intellectual property495,673
  3. DesignSection 4. Copycats, thin apps, spam415,532
  4. BusinessSection 3. In-app purchase, subscriptions283,820
  5. SafetySection 1. Objectionable and user content, kids151,159
  6. Other4,145
Performance gets cited almost three times as often as Legal, the next biggest. Source: Apple, 2025 App Store Transparency Report.

Performance is miles ahead. It's the section with crashes, placeholder screens, demo logins that don't work and screenshots from a design you dropped two months ago. You can catch nearly all of it yourself with a release build and a fresh install.

Don't add the bars up. They come to more than 2,093,244 because a single submission can be rejected under more than one guideline. The report says so in a footnote.

The same report has a nicer number too. 387,087 submissions were approved after a rejection. Somebody read the message, fixed the thing and got through on the next try.

Three years of reports, side by side

Apple has published the same figures for 2023, 2024 and 2025, so you can compare them. The rejection rate is our own arithmetic, rejected divided by reviewed.

Submissions reviewed and rejected

Millions of submissions per year

6.89M1.76M
7.77M1.93M
9.10M2.09M
202325.6 rejected per 100202424.9 rejected per 100202523.0 rejected per 100
ReviewedRejected
More apps every year, and a slightly smaller share turned away. Sources: Apple's transparency reports for 2023, 2024 and 2025.
202320242025
Submissions reviewed6,892,5007,771,5999,100,620
Submissions rejected1,763,8121,931,4002,093,244
Rejected, per 10025.624.923.0
Approved after a rejection277,923295,109387,087
Performance1,132,6131,235,4711,354,418
Legal420,914445,696495,673
Design295,497378,300415,532
Business192,884209,845283,820
Safety103,629116,105151,159
Other40,11923,6594,145

Submissions went up 32% in two years while the share rejected slipped from 25.6 to 23.0 per 100. So on paper, App Review isn't getting stricter.

Business is the line we'd keep an eye on. Rejections under it jumped 35% from 2024 to 2025, against 10% for Performance. That's the section with the in-app purchase and subscription rules, so if you're adding a paywall this year, it's the one most likely to bite. We wrote a separate guide to subscriptions that pass review.

And Performance has come first every single year. In 2025 it beat the other five sections put together, 1,354,418 to 1,350,329.

What each section covers

Performance (section 2)

The big one. It holds guideline 2.1, App Completeness, which is about crashes, placeholder content, missing demo accounts and servers that are switched off while the reviewer is trying your app. It also holds guideline 2.3, Accurate Metadata, which says your screenshots and description have to match what the app does, plus the hardware and software rules in 2.4 and 2.5.

Apple says that on average more than 40% of unresolved issues relate to 2.1 alone. We gave it a guide of its own.

Legal (section 5)

Mostly privacy. guideline 5.1.1 wants a privacy policy, purpose strings that say exactly why you need the camera or location, and account deletion inside the app if people can sign up inside the app. That last one is easy to miss. You build sign-up in the first week and nobody thinks about the other end until a reviewer asks. Section 5 also covers intellectual property, gambling and local laws.

Design (section 4)

The report's footnote says this means copycats, apps with minimum functionality and spam. In the guidelines that's guideline 4.1 Copycats, guideline 4.2 Minimum Functionality and guideline 4.3 Spam. 4.2 is what stops a website wrapped in a web view. 4.3 is what stops the same app going out under ten bundle IDs. The sign-in rules in guideline 4.8 live here as well.

Business (section 3)

How you charge. guideline 3.1.1 says anything you unlock inside the app has to be sold through in-app purchase, and guideline 3.1.2 has the rules for auto-renewing subscriptions.

Safety (section 1)

Objectionable content, apps for kids, apps that could get someone hurt, and apps where people post things. If your app has user content, guideline 1.2 asks for a way to report posts and block users.

The rejections Apple sees most, in its own words

Apple keeps a list of the issues it runs into most on its App Review page. Here it is in Apple's order, trimmed a little:

  1. Crashes and bugs. Submit only when the app is complete and ready to publish.
  2. Broken links. Every app needs a working link to user support with up-to-date contact details, and a link to its privacy policy.
  3. Placeholder content. Items still in progress can't be approved.
  4. Incomplete information. If features need a sign-in, give a valid demo account username and password.
  5. Privacy policy issues and unclear data access requests.
  6. Inaccurate screenshots that don't show what the app does.
  7. A substandard user interface.
  8. Web clippings, content aggregators or a collection of links.
  9. Repeated submission of similar apps, and copycats.
  10. Misleading users. The app must do what it says.
  11. Not enough lasting value, and an app submitted by the wrong company or person.

Most of that list is housekeeping. A support link that 404s, or a demo password that expired last Tuesday.

When it does go wrong, the message lands in App Store Connect and looks roughly like this. The guideline number at the top is the bit to read first.

A recreated App Review rejection message for guideline 2.1, with four numbered callouts on the guideline line, the review device, the next steps and the reply option
A typical 2.1 rejection, recreated. 1. The guideline that was broken. 2. The device the reviewer used, which may not be the one you tested on. 3. What Apple wants you to do. 4. You can reply if you think the reviewer got it wrong. Apple's exact wording changes from case to case.

What we check before pressing Submit

This is the routine we run on our own iPhone app. None of it is clever.

  • Test the build you upload. Delete the app, install the exact build from TestFlight on a real phone, and tap every link once. Release builds break in ways your debug build never shows you. Apple's 2.1 asks you to test on-device for bugs and stability.
  • Let the reviewer in. A demo account that still works on review day, notes for anything that isn't obvious, and your server switched on. Guideline 2.1 even says "turn on your back-end service!", exclamation mark included.
  • Make the listing match the app. Real screens in your screenshots. Not a splash screen, and not the feature you plan to ship next month.
  • Sort out privacy. A privacy policy link in App Store Connect and in the app, purpose strings that name the real reason, and account deletion in the app.
  • Sell digital things through in-app purchase, with the price on screen and a way to restore purchases.
Our App Store screenshot titled Comment on the exact line, showing a real page in the app with a comment threadOur App Store screenshot titled Nothing slips past you, showing the real inbox screen of the app
Two of our own App Store screenshots. Each one is a real screen from the build we upload, with a short line on top. That's what guideline 2.3 wants: the app in use, not a logo on a gradient.

What caught us out anyway

Setting up the first version of our own iPhone app, the review rules turned out to be the easy part. App Store Connect had its own ideas.

The name we wanted, Cloudy AI, was already taken, so the listing says useCloudy AI. We'd written release notes for 1.0, and App Store Connect refused them because the What's New field can't be edited on an app's first version. We push our listing from the terminal with the asc command line tool, and it applies a language's text in one go. So that single refused field blocked the whole update. We sent everything again without the release notes and saved them for 1.0.1.

Our App Store submission checklist has all of this as 79 steps you can tick off, each linked to the rule behind it.

What the report can't tell you

Apple counts rejections by section, never by individual rule. The report won't tell you how many were for 2.1 or for 5.1.1. The "over 40%" figure for 2.1 comes from Apple's App Review page, not from the report.

It counts submissions, not apps. An app rejected twice and then approved shows up as three submissions reviewed and two rejected. And because one submission can be rejected under several sections at once, the section totals overlap. You can't turn them into shares that add up to 100.

Questions people ask

What percentage of apps does Apple reject?

About 23 in every 100 submissions in 2025: 2,093,244 rejected out of 9,100,620 reviewed, according to Apple's transparency report. It was 25.6 in 2023 and 24.9 in 2024. These are submissions, so the same app can be counted more than once.

What is the most common reason for App Store rejection?

The Performance section of the rules, cited in 1,354,418 rejections in 2025. Within it, Apple says over 40% of unresolved issues relate to guideline 2.1, App Completeness, which covers crashes, placeholder content and missing information such as a demo account.

How long does App Review take?

Apple says it typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours (App Review page). An incomplete submission can take longer or get rejected.

What should I do after a rejection?

Read the guideline number in the message, fix that issue, and submit again. In 2025, 387,087 submissions were approved after a rejection. If you think the reviewer got it wrong, reply to the message or appeal. Apple's App Review page explains how.

Where does this data come from?

From Apple's App Store Transparency Reports for 2023, 2024 and 2025, and from Apple's App Review page. We checked every figure against them on 11 November 2026.