App Store rejection guides
The guidelines apps are most often rejected under, what reviewers look for, and what to check before you submit again.
- § 2.1
Guideline 2.1 App Completeness: why your app was rejected and how to fix it
Rejected under App Store Guideline 2.1? The usual causes are crashes, a missing demo account, placeholder content and in-app purchases the reviewer can't find.
- § 2.3
Guideline 2.3 Accurate Metadata: screenshots, descriptions and keywords that get rejected
How to fix an App Store rejection under Guideline 2.3: screenshots that don't show the app in use, descriptions that promise missing features, and keyword stuffing.
- § 4.2
Guideline 4.2 Minimum Functionality: why App Review rejects "repackaged websites"
Rejected under Guideline 4.2 Minimum Functionality? What App Review means by a repackaged website, and how to show enough native value to pass.
- § 4.3
Guideline 4.3 Spam: what it means and how to get your app approved
App rejected under Guideline 4.3 Spam? Why App Review flags duplicate apps and saturated categories, and how to show your app is meaningfully different.
- § 4.8
Guideline 4.8 Login Services: when you need Sign in with Apple
Rejected under Guideline 4.8? When an app with Google or Facebook login must also offer an equivalent option like Sign in with Apple, and when it doesn't have to.
- § 5.1.1
Guideline 5.1.1 Data Collection and Storage: privacy policy, purpose strings and account deletion
Fix a Guideline 5.1.1 rejection: privacy policy requirements, permission purpose strings, forced sign-in, and the in-app account deletion Apple requires.