Skip to main contentGet your mobile app iPhone Duo ready

MobileCodeCross Team

Why apps get rejected from the App Store

Common rejections are process failures — crashes, incomplete demos, privacy mismatch, thin functionality — not mysteries. Fix gates before upload.

Mobile

10 min

10min

  1. 01Crashes and bugs
  2. 02Incomplete information and demo login
  3. 03Misleading metadata
  4. 04Privacy and permissions

CodeCross Team

Stores reject apps for named reasons. Apple publishes the App Review Guidelines and a list of common issues. Google publishes the Developer Policy Center and an enforcement page. Common rejections are an unfinished binary, a missing demo login, or a form that does not match the app. This page covers the common buckets and what to do after a no.

Store path after a builder: vibe coding. Budget resubmits in how long it takes to build.

Crashes and bugs

Apple Guideline 2.1 says submissions should be final. Test on a device. Fix bugs before you upload. Apple will reject incomplete bundles and binaries that crash or show obvious technical problems. Apple’s App Review page says that on average, over 40% of unresolved issues relate to Guideline 2.1 — crashes, placeholder content, incomplete information, and more.

Play’s functionality policy does not allow apps that crash, force close, freeze, fail to install, or load and then do not respond. Test on more than one device. Turn on crash reporting on a release build before you submit.

Incomplete information and demo login

Apple’s before you submit list says give App Review full access. If the app has accounts, provide an active demo account or a full demo mode. Turn the backend on. Put special setup in App Review Information. Apple also requires a working support link and a privacy-policy link for every app.

Placeholder text, empty websites, and broken links are 2.1 issues. If a feature needs hardware that is hard to copy, Apple says be ready with a demo video or the hardware. Play’s production-access help says if the app needs sign-in, give working login credentials in Play Console so reviewers can test the features. Apple’s guidelines also require a working support URL. A 404 on that link is an incomplete-information problem. Put the demo login in App Review Information, not only in an email. If the backend sleeps, wake it before you click Submit.

Misleading metadata

Apple Guideline 2.3 says the description, screenshots, previews, and privacy information must match the real app. Screenshots should show the app in use, not only a logo or login wall. Do not hide features. Do not advertise a price or a capability the app does not have.

Play’s Deceptive Behavior policy says the title, icon, and description must match what the app does. Apps that claim a racing game and ship a puzzle, or that claim antivirus and ship a text guide, are examples Google lists. Do not impersonate another app or an official brand.

Privacy and permissions

Apple Guideline 5.1 requires a privacy policy in App Store Connect and in the app. The policy must say what you collect, how you use it, who you share it with, and how a user can ask you to delete data. If you create accounts, you must offer account deletion in the app. Permission prompts need a clear purpose string. Ask only for data the core job needs.

Apple also publishes privacy labels for the store listing. Play Data safety is the Android twin. Every developer with an app on Play — including closed, open, or production testing — must fill the form and say what the app and its SDKs collect. You are responsible for third-party SDKs. See the Developer Policy Center section on SDKs.

Payments under Guideline 3.1.1

Apple Guideline 3.1.1 says if you unlock features or content inside the app — subscriptions, extra levels, premium access — you must use in-app purchase. License keys, QR codes, and other side doors are not a substitute. Restorable purchases need a restore path. Play Payments requires Play billing for digital goods unless Section 3, 8, or 9 applies, and forbids Play billing for physical goods.

Unclear prices and a missing restore are common payment rejections. Wire the model before upload. See monetization strategies.

Minimum functionality under Guideline 4.2

Apple Guideline 4.2 says the app should include features, content, and UI beyond a repackaged website. A song or a movie belongs in other Apple stores. Catalogs that are mostly marketing, web clippings, or a pile of links do not meet the bar. Apple’s common issues page says websites served in an iOS app, and limited web interactions, do not make a quality app.

Play’s functionality policy does not allow apps with only limited functionality and content — for example a static PDF, a single wallpaper, or an app designed to do nothing. A thin builder wrap that only loads a site will fail both stores.

Other Play policy rejections

Play can reject, remove, or suspend an app. Enforcement says a rejected update does not take down the last live version. A removal takes the app off Play until you send a compliant update. Repeated rejections can lead to suspension. Check Policy status in Play Console.

New personal accounts still owe a closed test with 12 testers for 14 days before production. Target API floors are a separate clock. See Play API 36. Keep publisher seats under your company. See who owns App Store and Play Console.

What to do after a rejection

On Apple, open the App Review page in App Store Connect. That thread is the old Resolution Center. Apple’s reply help says you can correspond with App Review, attach screenshots, and fix the named guideline. If the issue is only metadata, you can resubmit the same build. You need the Account Holder, Admin, or App Manager role.

If you believe the app already follows the guidelines, appeal to the App Review Board. Reply in App Store Connect first. Then file one appeal per rejected app. Cite the guideline and explain point by point how you meet it. Do not appeal after you have already resubmitted a fix. Apple says a complete appeal does not guarantee a reversal.

On Play, read Policy status and the enforcement email. Appeals are for cases where you think Google made an error. Fix the named policy before you upload again. Google says do not republish a rejected or removed app until the violation is fixed. Do not open a second Apple appeal while a fix is already in review. Apple’s appeal help says file one appeal per rejected app, after you reply in App Store Connect. A new binary that still has the same crash is not an appeal. It is another rejection.

Pre-submit checklist

  • Release build with crash reporting. No crash on signup → core job → logout.
  • Working demo login and a live backend, plus notes for anything odd.
  • Support URL and privacy policy that match the binary.
  • Screenshots that show the real app.
  • Privacy labels and Data safety that match every SDK.
  • In-app purchase or Play billing where digital unlocks require it, plus restore.
  • More than a website in a shell.
  • Company-owned store seats. Account deletion if you offer accounts.
  • Apple upcoming requirements: iOS 13 or later (since 9 September 2026) and Xcode 26 / iOS 26 SDK (since 28 April 2026).

A vibe-coded preview is not a store binary. Harden first. See what production-ready means. If review keeps looping, Book a free call.

FAQ

Does a crash on one iPhone model count as an App Completeness problem under Guideline 2.1?

Yes. Apple Guideline 2.1 rejects binaries that crash or show obvious technical problems. Test on a device running current software before you upload.

If Play rejects the listing for a Data safety mismatch, does the last live version stay on the store?

Yes, for a rejected update. Google’s enforcement page says the version published before the update stays available. A removal is different: the app leaves Play until you send a compliant update.

Can I appeal to Apple’s App Review Board before I reply in App Store Connect?

No. Apple’s appeal help says reply to the rejection first. File the Board appeal only if that reply does not resolve it.

Does wrapping a working website in a WebView usually pass Guideline 4.2?

Usually no. Apple Guideline 4.2 wants more than a repackaged website. Apple’s common-issues list calls out websites served in an iOS shell.

What demo login details does App Review expect when the app has accounts?

A valid username and password in App Review Information, with the backend on. Apple’s guidelines also allow a full demo mode if a live account is not possible, with prior approval.

Book a call

Thirty minutes with a senior teammate — honest next steps.

Want a second pair of eyes on your app?

Tell us what you built and where it's stuck. We'll tell you what it takes to make it ready for real users.

Prefer writing? Send project details on the contact page.