Why Was My App Rejected? The Real App Review Reasons and Fixes
Most App Store rejections come from a handful of guidelines, and the biggest one is the dullest: the app was not finished or did not work when the reviewer opened it. Apple says that over 40 percent of unresolved issues are guideline 2.1, App Completeness (Apple's App Review page, read October 2026). Crashes, placeholder text, broken links and a login the reviewer cannot get past all land there. If you got a rejection, read the guideline number in the message first. It tells you which section below to start with.
Rejection is normal, not a verdict
Apple's 2025 App Store Transparency Report lists 9,100,620 submissions reviewed and 2,093,244 rejected, which is roughly one in four. The same 2025 report shows 387,087 of those were approved after the developer fixed the problem. So a rejection is a to-do list, not a ban.
The report splits rejections by guideline section. Performance was the largest at 1,354,418, followed by Legal at 495,673, Design at 415,532, Business at 283,820 and Safety at 151,159. Performance is the section that holds guideline 2.1, which is why "it crashed" and "it was incomplete" dominate.
On timing, Apple states that 90 percent of submissions are reviewed in less than 24 hours (same page, October 2026). A rejection usually costs you a day or two, not weeks, as long as you fix the real cause.
Guideline 2.1: the app was incomplete or broken
This is the most common one, and nearly all of it is preventable. Guideline 2.1(a) asks for final versions with "placeholder text, empty websites, and other temporary content" removed, and tells you to include demo account details "and turn on your back-end service" if the app has a login.
The fixes, in the order we check them:
- Test on a real phone, not only the simulator, and fix every crash.
- Delete lorem ipsum, "coming soon" screens and links that go nowhere.
- Put a working demo login in the App Review notes, and make sure it has not expired.
- Confirm your server or backend is live during review. A staging server that sleeps at night is a classic cause.
- If you sell anything in the app, make sure each in-app purchase is visible to the reviewer (guideline 2.1(b)).
Guideline 2.3: your listing does not match your app
Guideline 2.3 requires that your description, screenshots and privacy information "accurately reflect the app's core experience." Screenshots showing a feature the app does not have, or a description promising something that ships next quarter, are the usual triggers. Our guide to App Store screenshot requirements covers the sizes and the content rules, and the screenshot generator builds compliant ones.
Apple's report also counts rejections for hidden or undocumented features, which is part of the same section. If a feature is not obvious, describe it in the review notes in specific terms. Apple says generic descriptions will be rejected.
Guideline 4.2: it looks like a website in an app shell
Guideline 4.2 says an app should "elevate it beyond a repackaged website." An app that is mostly a web view around your existing site, a brochure, or a list of links is at risk. This one matters for small businesses, because a cheap wrapper is exactly what many first apps are.
The fix is real native behavior: push notifications, saved accounts, booking inside the app, offline access, a camera or location feature that serves the customer. One of those, built properly, usually answers the objection. If you only need your website on a phone, you may be better served by a web app saved to the home screen, and we say so in does a small business need a mobile app.
Guideline 4.2.6 adds a warning for anyone buying from an app-maker service: apps created from a commercialized template or app generation service "will be rejected unless they are submitted directly by the provider of the app's content." Check that before you pay for a template.
Guideline 5.1.1: privacy policy and account deletion
Guideline 5.1.1 needs a privacy policy linked in App Store Connect and inside the app. It must say what data you collect, who else receives it, and how a user can ask for deletion. If your app lets people create an account, you must also offer account deletion inside the app.
Both are easy to miss and easy to fix. The app privacy policy requirements post explains what to put in the policy, and the privacy policy generator gives you a starting draft. Have a lawyer read it if your app handles health, children's or payment data.
What to do when you disagree with the reviewer
Reply in App Store Connect first. Apple lists this as a way to resolve issues before you resubmit, and it often fixes a misunderstanding in one exchange. If you still believe the app follows the guidelines, you can file an appeal with the App Review Board, one appeal per rejected submission, with specific reasons.
Be realistic about appeals. Apple's 2025 transparency report covers appeals of app removals, not first-submission rejections, and it shows only 423 restorations from 26,305 appeals, because most removed apps were taken down for fraud or illegality. A first-time rejection for a missing demo login is a different case, but the lesson holds: fixing the issue is almost always faster than arguing.
Where we are the wrong fit
If you are a developer who wants to ship and debug your own app, you do not need an agency to read a guideline number. Use the app launch checklist and the guidelines above, and resubmit. We make sense when you would rather not carry the submission risk yourself, and our publishing guide walks through the whole submission, under your own developer account.
If you want a second pair of eyes before you submit, book a free intro call.
Your app. In the stores. Done for you. US APP Team designs, builds, and launches your iOS and Android app for a fixed price. Start your app brief or book a free intro call — both are free.
Want to poke around first? Every tool in our free tool library runs in your browser with no signup: an app cost calculator, an app name generator, and a privacy policy generator.
