A rejection email from Apple or Google means one build of your app didn't pass review. It is not a ban. The message names the rule you missed, usually by guideline number, and you can fix it, reply and resubmit. Most rejections come from a short list of missing pieces: a demo login, a privacy link, account deletion or a feature that doesn't work when the reviewer taps it.
What the rejection email actually means
Apple's email tells you the status changed. The detail sits in App Store Connect. Apple's App Review page says: "If your submission didn't pass review, details are provided, including any specific App Review Guidelines that your submission didn't follow. You can correspond with App Review to resolve the issues before resubmitting the build."
Google sends an email too, and puts the detail in Play Console. Google's help page on removed apps says to "Check your Notifications and email for information about the policy your app violated."
Copy three things from each rejection into a note:
- The guideline or policy named (for example, Apple 2.1 or 5.1.1(v)).
- What the reviewer saw: often a screenshot, a device model and the steps they took.
- What they ask you to do: fix the build, change the store listing, or answer a question.
The most common reasons apps get rejected
Apple 2.1: App Completeness
This is the big one. Apple's App Review page says: "On average, over 40% of unresolved issues are related to guideline 2.1: App Completeness, which covers crashes, placeholder content, incomplete information, and more." Guideline 2.1 asks for final versions with "fully functional URLs" and no placeholder text. A crash on launch, a "coming soon" screen or a broken support link all count.
Missing demo login
Also under 2.1: Apple asks you to "include demo account info (and turn on your back-end service!) if your app includes a login." Google has the same rule: if parts of your app sit behind a login, "you must provide all required details to enable access to your app" (Play Console help). Give the reviewer a working email and password, with sample data already in the account.
Apple 4.2: Minimum Functionality
Guideline 4.2 says your app "should include features, content, and UI that elevate it beyond a repackaged website." Apps that are a website in a frame are the usual target. The fix is real app features (push messages, offline content, device features) or a proper native app. See how to get a web app into the stores.
Apple 5.1.1: Privacy and account deletion
Guideline 5.1.1(i) asks for a privacy policy link both in App Store Connect and inside the app. 5.1.1(v) says: "If your app supports account creation, you must also offer account deletion within the app." Apple's account deletion page adds that "only offering to temporarily deactivate or disable an account is insufficient," and that most apps shouldn't make people email or call. More in our post on account deletion requirements.
Apple 4.8: Login services
If you offer Google or Facebook sign-in for the main account, guideline 4.8 says you "must also offer as an equivalent option another login service" with specific privacy features. Sign in with Apple meets them, so most teams add it.
Newer Apple rules from 2026
Apple revised its guidelines on February 6, June 8 and October 16, 2026 (latest change log). Three of the changes create new grounds for rejection. As read on 2026-11-11:
- 1.2, user-generated content (February 6, 2026). Apple clarified that apps with random or anonymous chat fall under this rule. Apps "that end up being used primarily for … Chatroulette-style experiences, random or anonymous chat … do not belong on the App Store". Any app with user content needs filtering, a way to report content, a way to block users and published contact details (guideline 1.2).
- 4.3, spam (revised June 8, 2026). "Don't submit apps that are indistinguishable from what's already widely available." Template and lookalike apps are the usual target (guideline 4.3).
- 2.5.19, hidden features (new, October 16, 2026). "Don't include any hidden, dormant, or undocumented features in your app; your app's functionality should be clear to end users and App Review." Show the reviewer everything, and describe new features in the review notes (guideline 2.5.19).
Google Play: Data safety and policy declarations
Google rejects fewer apps for design and more for forms. "All developers that have an app published on Google Play must complete the Data safety form," even if the app collects no data (Play Console help). Google also requires an in-app path to delete accounts and "a web link resource where users can request app account deletion" (Play Console help). If your Data safety answers don't match what the app's code and SDKs actually collect, expect a rejection.
One new form arrived in 2026: every account must declare whether it's a trader by February 1, 2027, and Google says missing it "may trigger enforcement including app update blocks and removal from the Play Store globally" (Trader status declaration). See Google Play trader status.
| Store | Rule | What usually fixes it |
|---|---|---|
| Apple | 2.1 App Completeness | Remove placeholders, fix crashes, add a working demo login |
| Apple | 4.2 Minimum Functionality | Add real app features, or build a native app |
| Apple | 5.1.1 Privacy | Privacy link in the app, in-app account deletion |
| Apple | 4.8 Login Services | Add Sign in with Apple |
| Apple | 1.2 User-Generated Content | Filtering, reporting, blocking and contact details; no random or anonymous chat |
| Apple | 4.3 Spam | Make the app clearly different from what's already on the store |
| Apple | 2.5.19 Hidden features | Show every feature to the reviewer and describe it in the review notes |
| Data safety, account deletion | Correct the form, add the web deletion link | |
| Trader status (from February 1, 2027) | Declare it in Play Console |
How to read the reply thread and respond
In App Store Connect, open your app and go to the App Review section (many people still call it the Resolution Center). Read the whole message, not just the guideline number. Then:
- Fix the actual cause. If the reviewer says a button did nothing, test that exact path on a clean install.
- Reply in the thread. Say what you changed, where to find it, and give fresh login details if needed.
- Upload a new build if code changed. If only the listing or a form changed, you may be able to resubmit without one.
- Use the review notes field on every future submission: demo login, where key features live, anything that needs explaining.
On Google Play, fix the issue, update the Policy status declarations or the listing, and send a new release for review.
How long resubmission takes
Apple says it typically reviews "at least 50% of submissions in less than 24 hours and 90% in less than 48 hours" (App Review). Some apps wait longer, and you can ask for an expedited review for a critical bug fix or a dated event. Google says some reviews take "up to seven days or longer in exceptional cases" (Play Console help). More on timing in how long App Store review takes.
The review is rarely the slow part. The fix is. A missing demo login takes an hour. Account deletion, Sign in with Apple or a 4.2 redesign can take weeks if the app wasn't built with them in mind.
Before you resubmit: a final check
- App opens and runs on a clean install with no crash
- No placeholder text, test screens or dead links
- Demo login works and the account has sample data
- Privacy policy linked in the store listing and inside the app
- In-app account deletion that actually deletes, plus a web link for Google
- Sign in with Apple if you offer Google or Facebook login
- Data safety form and privacy labels match what the app collects
- Review notes explain where to find each key feature
When to get help
If the fix is a form or a login, do it yourself. Get help when the fix is in code you can't change, it's the second rejection for the same rule, or nobody on your side can reply to the reviewer.
PerceptiaAI's Rejection Fix starts from $199. You get a note within 1 working day on what Apple or Google want, a fixed price, the fix, the resubmission and the reply to the reviewer. Not sure what else is wrong? An App Check ($249 or $449) gives you a plain-English report, including likely store rejections, with a clear fix, launch or rebuild answer. If the app is missing several must-haves, such as account deletion and Sign in with Apple, Store Launch ($1,190 or $1,990) covers them and submits to both stores.
Building a new app? Every PerceptiaAI build includes the store work from day one: see the app launch checklist.
For an App Check and what can follow it, with prices, see the concept app: Deskhaus, a rejected app rebuilt and relaunched. Shiftbay shows the same for a Bubble app the store turned down.
Changelog
- 2026-11-11: Rechecked Apple's App Review page and guidelines and Google's help articles 2477981, 9859455, 9859751, 10787469 and 13327111; every quote still matches.
- 2026-11-11: Added Apple's 2026 rule changes that cause rejections: 1.2 (random or anonymous chat), 4.3 (spam) and the new 2.5.19 (hidden features).
- 2026-11-11: Added Google Play's trader status declaration, due February 1, 2027, to the Google section and the table.
