15 Common Reasons iOS Apps Get Rejected by Apple
Updated: October 2026
Most App Store rejections come from a small group of repeat problems: bugs and crashes, incomplete content, broken logins, privacy issues, unclear metadata and missing features. Here are 15 common reasons, what they mean and how to prevent each one.
Bugs and completeness
1. Crashes and bugs (Guideline 2.1). The app closes, freezes or has broken features. Fix: test on a real iPhone before submitting.
2. Placeholder content (2.1). Empty screens, test text or images. Fix: search your app for temporary content.
3. No demo account (2.1). The reviewer cannot sign in. Fix: add working demo details in the review notes.
4. Backend offline (2.1). The server is down during review. Fix: keep it live until the app is approved.
5. Broken in-app purchases (3.1.1 and 2.1). Purchase buttons fail or content does not unlock. Fix: test the whole purchase flow.
Metadata and accuracy
6. Misleading screenshots or description (2.3). They show features the app does not have. Fix: make store pages match the real app.
7. Missing or broken links (2.1 and 5.1.1). Support or privacy policy page does not open. Fix: open every link before submitting.
8. Unclear review notes (2.1). The reviewer does not know how to reach a feature. Fix: write short, clear notes.
Privacy and data
9. No privacy policy (5.1.1). Apps need a privacy policy link. Fix: add it in App Store Connect and in your app.
10. Permission requests without a clear reason (5.1.1). The permission text does not explain why you need camera, location or notifications. Fix: write a clear, honest purpose string.
11. No way to delete an account (5.1.1). If your app lets people create an account, it should let them delete it inside the app. Fix: add an account deletion option.
Design and functionality
12. Minimum functionality (4.2). The app feels like a simple website wrapper with little value. Fix: add real, app-like features.
13. Spam or copycat apps (4.3). Many near-identical apps from one developer. Fix: offer something distinct.
14. Poor design on some devices (4.0). Cut-off text, overlapping buttons, content hidden behind the keyboard. Fix: test on a real device.
15. Login rules (4.8). Apps that offer third-party login may need to offer an equivalent privacy-focused login option. Fix: read the current guideline carefully.
Guideline numbers and wording can change. Check Apple’s current App Review Guidelines before you submit.
Which of these can testing catch?
Testing on a real device catches most of items 1 to 5, 7, 8 and 14: crashes, broken flows, dead links, purchase problems and layout bugs. Policy and content issues (items 9 to 13 and 15) need a careful read of the guidelines instead.
Checklist before you submit
- Tested the final build on a real iPhone
- Demo account added and working
- Backend live
- No placeholder content
- All links open
- Permission texts are clear
- Account deletion works, if you have accounts
- Screenshots and description match the app
- Review notes written
Frequently asked questions
What is the single most common rejection reason?
Bugs and incomplete apps under Guideline 2.1 are among the most frequent, and the most preventable.
Can I appeal a rejection?
Yes. You can reply in App Store Connect or submit a fixed build. Make sure you address exactly what the reviewer wrote.
How can I find bugs before review?
Test on a real iPhone and ask someone who has never used the app to test it. RealAppTest provides this with a detailed report.