App rejected by Google Play or App Store: common reasons and how to fix them
You submitted an app or an update for review and got a "Rejected" email with a vague reference to the guidelines. Here's why Google and Apple reject apps most often, where to find the exact reason, and how to fix it so the next review passes.
Where to find the rejection reason
Don't rely on the short email alone. The full reason is in the console:
- Google Play Console: Policy status and the Inbox notifications. They show which policy was violated and in which version.
- App Store Connect: the Resolution Center on the version page. Apple gives the guideline number (for example 2.1 or 5.1.1) and often a screenshot of what the reviewer saw.
The guideline number is the main clue: it tells you right away what to fix.
Common reasons on Google Play
1. No privacy policy, or it doesn't open
If the app collects any data at all (even an email or a device ID), you need a working privacy policy link in the console and, ideally, in the app itself.
2. The Data safety form doesn't match what the app does
In Data safety you declare what data the app collects. If you added analytics, ads or Google sign-in but wrote "we collect nothing", the app will be rejected. Check every SDK in the project.
3. Unnecessary or sensitive permissions
Access to SMS, call logs, background location or all files needs a separate justification and is allowed only for certain app types. Often it's enough to remove a permission left over from an old library.
4. Outdated Android version (target API)
Google regularly raises the target Android version requirement. An old project that hasn't been updated in a while simply won't pass until it's updated.
5. No access for the reviewer
If the app has a login, the reviewer needs a test username and password. You add them under App access.
6. New personal developer account without closed testing
For new personal accounts Google requires closed testing with a group of testers for a set period before the app can be published to everyone. The exact requirements are shown in the console.

Common reasons on the App Store
1. The app crashes or feels unfinished (guideline 2.1)
The reviewer tapped a button and the app closed, or test text was left in. Test on a real iPhone with the latest iOS and provide a demo account in the review notes.
2. "It's just a website in a wrapper" (guideline 4.2)
Apple rejects apps that only open a website without features of their own. What helps is functionality that makes sense on a phone: notifications, offline mode, camera, convenient navigation.
3. Privacy and account deletion (guideline 5.1.1)
You need a privacy policy, honest App Privacy details, and if users can create an account in the app, they must also be able to delete it right in the app.
4. Description and screenshots don't match the app (guideline 2.3)
Screenshots must show the real app, and the description must not promise what isn't there.
5. Paying for digital goods outside Apple (guideline 3.1.1)
Subscriptions and digital content inside the app usually have to be sold through Apple's in-app purchases. Physical goods and services, like in a regular store, can be paid for any way you like.
6. Social login without an alternative
If you offer Google or Facebook login, Apple may require another privacy-friendly login option, such as Sign in with Apple.
How to reply and resubmit
- Fix exactly what the reason says and nothing more: big changes can raise new questions.
- Increase the build number and upload the new version.
- Briefly tell the reviewer what you changed. On the App Store that's in the Resolution Center, on Google Play in the resubmission form.
- If you think the rejection was a mistake, you can appeal: calmly, with an explanation and screenshots.
Most of the time the next review passes in 1-3 days if you fixed exactly what the reviewer asked for.
If the app wasn't just rejected but is also buggy, start with "App is buggy: how to find the cause".