10 Things That Get Your App Rejected from the App Store in 2026

I've reviewed over 150 apps through RealAppReview, and I see the same rejection patterns over and over. Developers spend months building their app, submit it excitedly — and get a cold, robotic rejection email 48 hours later.

Here are the 10 most common reasons apps get rejected in 2026, based on real submissions I've analyzed. Each one includes the exact Apple/Google guideline, why it happens, and how to fix it before you hit "Submit."

---

1. 💥 Your App Crashes During Review

Guideline: Apple Review Guideline 2.1 — Performance: App Completeness

This is the #1 killer. The reviewer opens your app on their test device, taps around for 2 minutes, and it crashes. Game over.

Why it happens:

• You only tested on your own device and the simulator
• Memory issues on older devices (iPhone SE, budget Androids)
• Network-dependent features failing on Apple's corporate Wi-Fi
• Race conditions that only show up on fresh installs

How to fix it:

• Test on at least 3 real devices across different OS versions
• Do a clean install test — delete the app entirely, reinstall, go through onboarding
• Test with airplane mode on, then toggle back. Does your app handle network transitions?
• Use Xcode's Memory Graph Debugger and Android Studio's Profiler before submission

💡 A real-device review from RealAppReview catches crashes that simulators miss — because we test on actual hardware, not emulated environments.

2. 🔒 Missing or Broken Privacy Policy

Guideline: Apple 5.1.1 — Data Collection and Storage

In 2026, Apple and Google are extremely strict about privacy. If your app collects any data — even just an email for login — you need a visible, accessible privacy policy.

Common mistakes:

• Privacy policy link goes to a 404 page
• Policy doesn't mention the specific data your app collects
• No in-app link to the policy (only in the App Store listing)
• Using third-party SDKs (analytics, ads) without disclosing their data collection

How to fix it:

• Host your privacy policy on a permanent URL (not a Google Doc)
• Link it in your app's Settings screen AND in App Store Connect / Play Console
• List every SDK you use and what data they collect (Firebase, Amplitude, Facebook SDK, etc.)
• Include an account deletion option — Apple requires it since 2024

3. 📝 Incomplete or Placeholder Content

Guideline: Apple 2.1 — Performance: App Completeness

Apple reviewers are human. They see your app has a "Premium" tab that says "Coming Soon!" — instant rejection. Same for lorem ipsum text, empty settings screens, or features that require a server that isn't live yet.

Red flags:

• "Coming soon" or "Under construction" anywhere in the app
• Empty states with no content or explanation
• Buttons that lead nowhere
• Test data visible ("Hello John Doe", "test@test.com")

The fix: Before submitting, tap every single button in your app. Every screen. Every menu item. If something isn't ready, remove it entirely — don't leave placeholders.

4. 🖼️ Misleading Screenshots or Metadata

Guideline: Apple 2.3.7 — Accurate Metadata

Your screenshots show a beautiful dark mode UI with AI features — but the actual app is a basic form with no dark mode. Rejected.

What counts as misleading:

• Screenshots showing features that don't exist yet
• Using mockups instead of real in-app screenshots
• Claiming "AI-powered" when it's just a basic algorithm
• Keyword stuffing in your app name or subtitle
• Rating or ranking claims without evidence ("Best fitness app!")

How to fix it: Take screenshots from the actual current build. Your description should match exactly what the reviewer will see when they open your app.

5. 💳 Payment Shenanigans

Guideline: Apple 3.1.1 — In-App Purchase

If your app sells digital content or subscriptions, you must use Apple's In-App Purchase system (with few exceptions). Trying to sneak users to a website to pay? That's a fast track to rejection.

Common payment mistakes:

• No "Restore Purchases" button (Apple requires this)
• Subscription terms hidden or unclear
• Directing users to a website to buy digital goods
• Free trial not clearly explaining what happens when it ends
• Price displayed in app doesn't match App Store pricing

Fix: Add a visible "Restore Purchases" button. Make subscription terms crystal clear before the paywall. Test the full purchase flow including cancellation.

6. 🔐 Requesting Unnecessary Permissions

Guideline: Apple 5.1.1 — Data Collection

Your note-taking app asks for camera, microphone, location, and contacts access on first launch? Apple will ask: "Why does a note app need my microphone?"

Rules of thumb:

• Only request permissions when the user is about to use that feature
• Always explain WHY you need the permission in the alert text
• If the user declines, your app should still work (with reduced functionality)
• Never request permissions on app launch — wait for the relevant user action

7. 🐌 Unacceptably Slow Performance

Guideline: Apple 2.1

If your app takes 10+ seconds to load, shows blank screens while fetching data, or stutters during scrolling — reviewers notice. Apple's standard: your app should feel responsive within 3 seconds of launch.

Performance killers:

• Loading everything on the main thread
• No skeleton screens or loading indicators
• Unoptimized images (5MB PNGs loading from a remote server)
• Excessive API calls on launch

Fix: Implement lazy loading, use skeleton screens, compress images, and cache aggressively. Profile with Instruments (iOS) or Android Profiler before submitting.

8. 🚫 Copycat or Spam Apps

Guideline: Apple 4.0 — Design: Spam

Both stores have cracked down hard on apps that are slight variations of existing apps, template-based apps with no unique value, or apps that duplicate built-in OS features without adding anything meaningful.

You'll get rejected if:

• Your app is a near-identical clone of a popular app
• It's a template app with just your logo swapped in
• It's a simple wrapper around a website (WebView-only apps)
• You submit multiple variations of the same app

How to differentiate: Add genuine value. Even if your concept is similar to existing apps, your implementation, UX, or target audience should be meaningfully different.

9. 👶 Missing Age Rating or Content Issues

Guideline: Apple 1.0 — Safety

Your app contains user-generated content but you rated it 4+? That's a rejection. The age rating questionnaire is not a formality — answer it honestly.

Common mistakes:

• Incorrect age rating for the content type
• User-generated content without moderation or reporting features
• Links to external websites with adult content
• Violence or mature themes without proper rating

10. 📱 Not Optimized for Current Devices

Guideline: Apple 2.4.1 — Hardware Compatibility

In 2026, Apple requires apps to be built with the iOS 18 SDK and support current device sizes. That means:

• iPhone 16 Pro Max and iPhone SE (3rd gen) must both look good
• Dynamic Island support is expected
• iPad layouts should use the full screen (no letterboxing)
• Dark mode support is strongly recommended
• Android: targeting API 35 (Android 15) is required for new submissions

Fix: Test your layouts on the smallest and largest supported screen sizes. Use Auto Layout (iOS) or ConstraintLayout (Android). Support both orientations if your app category warrants it.

---

🎯 The Bottom Line

App store rejections aren't mysterious — they follow patterns. The 10 issues above account for roughly 85% of all rejections I see in apps submitted to RealAppReview for pre-launch review.

The best way to avoid rejection? Test like a reviewer would. Fresh install, clean device, no assumptions. Tap every button. Read every screen. Break your own app before Apple's reviewer does.

And if you want a second pair of eyes before you submit — that's literally what we do.