Rejection guides
App Store Rejection Guides
Rejection is a normal part of shipping on the App Store: roughly 22% of all submissions were rejected in 2025, 63% of developers hit at least one rejection per year, and over 40% of first submissions bounce. The good news: most rejections map to a handful of guidelines with well-understood fixes.
One more number worth knowing — about 85% of appeals are denied. In almost every case, fixing the issue and resubmitting is faster than arguing. These guides show you exactly what to fix for each guideline.
Guideline 2.1
App Completeness
Crashes, bugs, placeholder content and missing demo accounts — the single most common rejection.
Guideline 2.3.3
Inaccurate Screenshots
Screenshots must show the app actually in use, not just splash screens or marketing art.
Guideline 2.3.10
Accurate Metadata
Android mentions, pricing in the description and irrelevant keywords in your metadata.
Guideline 2.5.1
Software Requirements
Private APIs, non-public frameworks and deprecated technologies like UIWebView.
Guideline 3.1.1
In-App Purchase
Digital content unlocked outside in-app purchase, or external payment links Apple doesn't allow.
Guideline 4.2
Minimum Functionality
Web wrappers and thin apps that don't do enough to justify existing as native apps.
Guideline 4.3
Spam / Design
Duplicate, template and repackaged apps flagged as spam — including 4.3(a).
Guideline 5.1.1
Privacy: Data Collection and Storage
Missing purpose strings, forced registration and account-deletion gaps — the second most common rejection.
Guideline 5.1.2
Data Use and Sharing
Tracking without the ATT prompt and sharing user data with third parties without consent.
Or stop reading rejection emails entirely
Forward Apple's email to AscAuto — it classifies the guideline, drafts the fix (metadata fixes can apply automatically), and resubmits after your one-click approval.