Rejection Is Part of the Process — Until It Doesn't Have to Be
If you've spent weeks building an app and the first email you get from Apple after submission is a rejection notice, the feeling is difficult to describe. A mix of frustration, confusion, and urgency — especially if you had a launch date planned.
The good news: most App Store rejections are preventable. Apple publishes its App Store Review Guidelines in detail, and the most common rejection reasons are well-documented. Understanding them before you submit can save you days or weeks of back-and-forth with the review team.
This guide covers the most frequent rejection reasons, what they actually mean in practice, and how to address them before they become a problem.
---
How the App Store Review Process Works
When you submit an app through App Store Connect, it enters a review queue. Apple's reviewers — real humans — test your app on actual devices. They check it against the App Store Review Guidelines, which cover everything from content policies to technical performance.
The average review time is 24–48 hours for most submissions, though it can take longer for complex apps or during high-volume periods (like the weeks before major Apple events). If your app is rejected, you receive a message in App Store Connect explaining which guideline was violated.
You can then resolve the issue and resubmit, or file an appeal if you believe the rejection was incorrect.
---
The Most Common Rejection Reasons
1. Guideline 2.1 — App Completeness
What it means: Your app doesn't work as described, crashes on launch, has broken features, or includes placeholder content like "Lorem ipsum" text or buttons that do nothing.
How to avoid it: - Test on a real device before submitting — simulators don't catch everything - Test on the oldest iOS version you claim to support - Walk through every screen, every button, every edge case - Remove all placeholder content - If your app requires a login, provide Apple's review team with a test account in the App Review Notes
This is the single most common reason for rejection. A 30-minute QA pass before submission can prevent it entirely.
---
2. Guideline 4.2 — Minimum Functionality
What it means: Your app does too little to be valuable. Apple considers apps that are essentially just websites wrapped in a WebView, single-function utilities with no real utility, or apps that duplicate built-in iOS functionality without meaningful added value.
How to avoid it: - Build something genuinely useful. If your app is a web wrapper, you need native features that go beyond what Safari offers. - Be clear in your app description about what unique value you provide - If your app is intentionally simple (a single utility), make sure it executes that single function exceptionally well
---
3. Guideline 3.1.1 — In-App Purchase Required
What it means: You're not using Apple's In-App Purchase system for digital goods and services. If your app sells anything that's consumed within the app — subscriptions, premium features, virtual goods, credits — it must go through IAP. You cannot direct users to purchase on a website to unlock in-app features.
How to avoid it: - Use StoreKit for all in-app purchases of digital content - Physical goods and services delivered outside the app (like ride-sharing or food delivery) are exempt - Reader apps have a special exception but it's narrowly defined - Don't mention external payment methods in your app or its metadata
---
4. Guideline 5.1 — Privacy — Data Collection and Storage
What it means: Your app collects more data than necessary, doesn't disclose data collection properly, or doesn't have a privacy policy when required.
How to avoid it: - Add a privacy policy URL in App Store Connect (required if you collect any user data) - Only request permissions you actually need — requesting microphone access for an app that doesn't record audio is a red flag - Complete the App Privacy section in App Store Connect accurately, including all data types your app and third-party SDKs collect - If you include analytics SDKs (Firebase, Mixpanel, etc.), their data collection must be disclosed
---
5. Guideline 2.3 — Accurate Metadata
What it means: Your app's name, description, screenshots, or preview video don't accurately represent what the app does. This includes screenshots that show features not in the app, app names that include unrelated keywords for ASO purposes, or descriptions that make claims you can't support.
How to avoid it: - Screenshots must show actual app UI — no lifestyle photos unless they're combined with real UI - Don't stuff keywords into your app name unless they're genuinely part of the name - App description claims ("Best in class", "#1 habit tracker") require backing — vague superlatives can be flagged - If your screenshots show an iPhone 16 device frame, make sure the UI inside it is real
This guideline is also why investing in accurate, high-quality screenshots matters — tools like AppFrame help you create professional images that showcase your real UI without any misleading embellishment.
---
6. Guideline 1.1 / 1.2 — Objectionable Content
What it means: Your app contains content that Apple considers inappropriate — violent, hateful, discriminatory, or adult content that isn't properly gated behind an age rating.
How to avoid it: - Set your age rating appropriately in App Store Connect - If your app allows user-generated content, you must have a moderation system and a way for users to report inappropriate content - Don't rely on the honor system for age verification — Apple expects technical enforcement
---
7. Guideline 4.3 — Spam
What it means: You've submitted multiple apps that are essentially the same, or your app is a trivial clone of an existing app with minor visual changes.
How to avoid it: - Each app you submit should have a unique, clearly differentiated purpose - If you're building a series of apps (e.g., regional variations), make sure each is meaningfully different or use a single app with localization - Reskinning app templates and submitting them as original apps is specifically called out
---
Practical Pre-Submission Checklist
Before you hit submit, go through this list:
- [ ] App launches without crashing on a real device
- [ ] All features shown in screenshots are functional
- [ ] Test account credentials provided in App Review Notes (if login required)
- [ ] Privacy policy URL added in App Store Connect
- [ ] App Privacy section completed accurately
- [ ] All permissions have explanatory usage descriptions in Info.plist
- [ ] Age rating set appropriately
- [ ] In-app purchases use StoreKit (no external payment links)
- [ ] App description is accurate — no false claims
- [ ] Screenshots show real app UI
---
What to Do When You Get Rejected
First: don't panic. Rejection emails are formulaic but they contain specific guideline references. Read them carefully.
If the rejection is clear: Fix the issue, test the fix, and resubmit. Include a note in the "App Review Notes" field explaining what you changed and why the app now complies.
If the rejection seems wrong: You can reply directly to the review team within App Store Connect. Be polite, specific, and reference the relevant guideline. Attach screenshots or screen recordings if they help illustrate your point.
If you disagree with the decision: File an appeal through the App Store Review Appeal Process. Appeals are reviewed by a separate team and should be used when you believe the guideline was misapplied, not when you simply want to negotiate.
---
Building for Approval from Day One
The best way to handle rejections is to not get them. That means reading the App Store Review Guidelines before you build, not after. Key sections to bookmark:
- Section 2: Performance — covers crashes, completeness, and software requirements
- Section 3: Business — covers IAP, subscriptions, and monetization rules
- Section 5: Privacy — covers data collection and permissions
Apple updates the guidelines periodically. If you submit infrequently, re-read the relevant sections before each submission — something that was fine a year ago may have a new requirement today.
Building with the guidelines in mind doesn't constrain your creativity. It channels it toward building apps that genuinely respect users, work reliably, and deliver real value — which is what the best apps on the store have always done.