Apple Rejected Your App for 2.1? How to Fix It Before You Resubmit
The short answer
App Store rejection: what to fix before you resubmit
Read the guideline number in your rejection message first: its first digit tells you what to fix. Section 2 (Performance) shows up most, so check your build, demo account, screenshots and review notes. Section 5 covers privacy, such as account deletion inside the app. Fix the cause, reply to App Review saying what changed, and appeal only if replying doesn't settle it.
Key facts
- 23 in 100App submissions Apple rejected in 2025 (2,093,244 of 9,100,620; our maths).Apple, 2025 App Store Transparency Report
- About 65Performance (section 2) rejections for every 100 rejected submissions. One submission can count in several sections (our maths).Apple, 2025 App Store Transparency Report
- Over 40%Of unresolved review issues relate to guideline 2.1, App Completeness, on average. Apple's figure for unresolved issues, not rejections.Apple, App Review: avoiding common issues and review times
- 90% in 48 hoursShare of submissions Apple says it typically reviews in under 48 hours. Typical, not a promise.Apple, App Review: avoiding common issues and review times
Chapters
Transcript
Edited for readingSage is a fictional plant care app; its story is illustrative. Every rule and number comes from Apple's own pages, listed under Sources.
App Store rejection: what now?Watch from 0:00
Your app got an App Store rejection. Start with one number. The rejection message cites a guideline, and says how your app breaks it. Its first digit tells you which part of your app to fix.
So here's the short answer. If the number starts with a 2, check your build, your demo account and your screenshots first. That section turns up in more rejected submissions than any other.
And if only your listing was wrong, you can resubmit the same build. No new code.
Below are the four sections that catch the most, the fix for each, and how to reply.
Which section catches the most submissions?Watch from 0:35
In Apple's 2025 report, it reviewed just over 9 million app submissions. About 23 of every 100 were rejected.
Performance, section 2, adds up to about 65 for every 100 rejected submissions. Legal, design and business follow, far behind. Safety is the smallest.
A submission can break several guidelines, so the sections add up to more than 100.
Our take: read the number before anything else. It tells you whether to fix your build, your listing or your policies.
So start with section 2, and the guideline Apple flags more than any other.
Is it guideline 2.1, App Completeness?Watch from 1:22
Apple says that on average, over 40% of unresolved issues relate to one guideline. Guideline 2.1, App Completeness.
It covers crashes, placeholder content, and information the reviewer needs but doesn't have. Apple doesn't publish rejections by single guideline, only by section. So that line is the closest thing to a ranking.
Take Sage, a made-up plant care app, on its first submission. The reviewer opened it, hit the sign-in screen, and stopped. Signing in needed a code, and the code went to the founder's phone. Rejected, under 2.1.
The fix is in App Store Connect, on your version page, under App Review Information. If your app has a login, give a demo account there. The account itself must not expire. Keep your back end switched on while they review.
If sign-in needs an extra code, explain in the Notes field how the reviewer gets past it.
If you sell auto-renewable subscriptions, let that account's subscription be expired. That way the reviewer sees the whole purchase flow. Every in-app purchase must be complete and visible to the reviewer.
Every link in your app must work. And you need a support link and a privacy policy link. Then the basics. No placeholder text, and a build that doesn't crash.
Checkpoint: could a stranger sign in and reach every paid feature without messaging you?
But a build that works can still fail on what you say about it.
Is it your screenshots or your notes?Watch from 2:52
That's guideline 2.3, Accurate Metadata. Your screenshots should show the app in use. Not merely a title screen, a login page or a splash screen. For each device size, more than half of your screenshots must show the app in use.
Sage's first screenshot was its logo on green. Now it opens on the watering schedule.
Then the Notes field. Describe new features and changes specifically. Apple says generic descriptions will be rejected. Explain anything a reviewer might not find on their own. Also list the outside services your core features rely on, like an AI service.
Our take: write the notes as if the reviewer has never seen your app. Because they haven't.
That covers section 2. Next is legal, section 5, where the privacy rules live.
Is it privacy, guideline 5.1.1?Watch from 3:43
Sage fixed its sign-in and submitted again. Rejected, again. This time, 5.1.1.
People could create an account in Sage, but there was no way to delete it. If your app supports account creation, you must offer account deletion inside the app. Only deactivating the account isn't enough.
Two more privacy checks. A privacy policy link, both in App Store Connect and inside the app. And every permission prompt must clearly and completely describe how you use the data.
Sage's camera prompt only said the app needed access. Now it says why: to photograph a plant and identify it.
Checkpoint: make an account, then try to delete it. Count the taps.
Performance and legal show up most. But business and design catch apps that look finished.
Is it how you charge, or what the app does?Watch from 4:34
Section 3 is business. Its main rule is about in-app purchase. As a rule, digital features you unlock inside the app go through Apple's in-app purchase. Some regions have exceptions, so check the rules for where you sell.
And before you ask anyone to subscribe, say clearly what they get for the price. Sage's paywall now lists what Sage Plus adds, right next to the price.
Section 4 is design. It's where copycats, thin apps and spam sit. Your app should do more than wrap a website.
If Apple called it spam, that's guideline 4.3. It has its own video: Apple Rejected Your App for 4.3 Spam? The Fix.
So you've found the cause. Now, how do you answer Apple?
How do you reply, and when do you appeal?Watch from 5:20
Open the rejection in App Store Connect and click Reply to App Review. Say what you changed, guideline by guideline, and attach screenshots.
If only your metadata was wrong, resubmit the same build. If you changed code, that's a new build.
Don't use the reply to appeal. If replying doesn't settle it, you can appeal to the App Review Board, through Apple's contact form. You get one appeal per rejected app. So cite the guideline and answer it point by point.
And don't send the same mistake twice. Repeat rejections for the same guideline make review take longer.
Already live? Apple says bug fixes won't be held up, except over legal or safety issues.
Apple says it typically reviews 90% of submissions in under 48 hours.
Our take: a careful fix beats a fast one you have to send twice.
Sage's third submission went in with a working demo account, a delete button and clear prompts. Approved.
And Sage isn't unusual. In that same report, Apple approved 387,000 submissions after a rejection.
Sources
- Apple, 2025 App Store Transparency Report (submissions reviewed 9,100,620; rejected 2,093,244; rejections by guidelines section; approved after rejection 387,087)
- Apple, App Review Guidelines (8 June 2026)
- Apple, App Review: avoiding common issues and review times
- Apple, App Review Information reference (demo account, Notes)
- Apple, Complete review information
- Apple, Screenshots guideline reference (2.3.3)
- Apple, Account deletion (5.1.1(v))
- Apple, Reply to App Review messages
- Apple, Appeal to the App Review Board
Caveat: Apple counts submissions, not apps, and one submission can break several guidelines, so the section figures add up to more than 100 per 100 rejected ("per 100" is our maths). The "over 40%" line is Apple's figure for unresolved issues, not rejections. Review times are what Apple says it typically achieves, not a promise. App Review decides every submission; nothing here guarantees approval.

