A Play Store rejection almost always comes from one of nine causes: an old target API level, a privacy policy or Data safety form that does not match the app, a reviewer who cannot log in, a risky permission, a missing account deletion option, a crash, a payments rule, a listing mismatch, or the 12-tester rule for new accounts. Google rejected about 1.69 million of 21.46 million submissions it reviewed in 2025, roughly 8 in 100, so rejection is common and fixable. Read the message in Play Console, match it to the table below, fix that one thing and resubmit.
This post is for founders and business owners whose app has just been rejected, or who want to avoid it before pressing Publish. You do not need to be technical.
Key takeaways
Since 31 August 2026, new apps and updates must target Android 16 (API level 36). Google's extension option runs only to 1 November 2026.
New personal developer accounts need a closed test with at least 12 testers for 14 days before they can apply for production access.
A reviewer who cannot log in is one of the cheapest rejections to fix: add working test credentials.
Apps with in-app sign-up need a way to delete the account, inside the app and on a web page.
Fix every issue in the message, then resubmit once. Repeated resubmits without changes waste days.
Why was my app rejected on the Play Store?
Your app was rejected because a build, a declaration or a listing broke a Google Play policy, or because your account has not met an eligibility rule. Google's email and the Play Console message name the policy. That name is the most useful clue you have.
Two things look alike but differ. A policy rejection means your app or listing breaks a rule. A production access rejection means your new developer account has not finished its testing requirement. Read the message before changing any code.
The rejection figures above come from Google's 2025 transparency report, published 31 March 2026, as summarised by PrimeTestLab. They cover all submissions, so they are not the chance that your first one fails.
What are the most common reasons for a Play Store rejection?
The most common causes of a Play Store rejection are crashes, thin functionality, a reviewer who cannot access the app, unexplained permissions, privacy and Data safety mismatches, and payment rule breaks. Google does not publish a ranked list, so this table is ordered by how cheaply each one can be fixed.
What you see or suspect | Likely cause | The fix |
"We could not access your app" | Login-gated app with no test account | Add working credentials and steps under App content, Sign- in details. Explain any OTP or two-step login in the instructions box. |
App crashes or freezes in review | Untested release build, or a build that fails on a low-RAM phone | Test the release build, not the debug one, on a cheap Android phone before upload. |
"Limited functionality" | App is a website wrapper, a template, or has very little content | Add real features or content. A plain WebView of a site often fails. |
Permission declaration rejected | You ask for SMS, background location or similar without a clear user benefit | Remove the permission, or explain the visible feature that needs it. |
Privacy policy rejected | Policy is a PDF, needs login, or does not name your app | Host it as a normal public web page, with a valid SSL certificate, that names your app and says what data you collect. |
Data safety mismatch | The form says "no data collected" but an SDK (analytics, ads, crash reports) collects it | List what your app and every SDK in it collect and share. |
Payments policy | Digital content or subscriptions sold through UPI or Razorpay inside the app | Digital content in the app generally needs Google Play Billing. Physical goods and real- world services are treated differently. Check Google's payments policy. |
Listing mismatch | Screenshots, content rating or ads declaration do not match the build | Update the listing so it describes the app that is actually uploaded. |
Target API level | App targets an old Android version | Rebuild against API 36. See the next section. |
When we build apps, the part that usually takes longest is not the code. It is the Data safety form, because someone has to list every SDK and what it collects, and the developer who added them has often moved on.
Why does Play Console say my app must target Android 16 (API level 36)?
Because since 31 August 2026 Google Play requires new apps and app updates to target Android 16, which is API level 36. The target API level is the Android version your app declares it was built and tested for. Per Google's target API requirements page (checked 29 October 2026), the rules are:
App | Requirement |
New apps and updates (phones and tablets) | Target Android 16 (API 36) or higher |
Existing apps, to stay visible to new users on newer Android phones | Target Android 15 (API 35) or higher |
Apps that miss this | Hidden from new users on phones running a newer Android version than the app targets |
Extension | Can be requested until 1 November 2026 |
If your app was built by a freelancer in 2023 or 2024, it probably targets API 33 or 34. Raising the target is not a one-line change. Android changes how notifications, background work, file access and permissions behave, so the app needs to be re-tested screen by screen.
Why was my production access rejected as a new developer?
Because new personal developer accounts must run a closed test with at least 12 testers, each opted in for 14 days in a row, before applying for production access. Per Google's testing requirements page, this applies to personal accounts created after 13 November 2023.
The rules that trip people up:
A tester who opts out and opts back in restarts their 14-day count.
Testers who leave before 14 days do not count.
Google also looks at tester engagement and feedback, not just the headcount.
Review of the production application usually takes seven days or less.
The practical plan: recruit 15 to 20 real people, such as staff, customers and friends, so that 12 stay in. Ask them to open the app and use it, and keep a short note of the feedback you act on. Google's page does not say whether organisation accounts have the same requirement, so check your account type in Play Console.
Do I need an account deletion option for Play Store?
Yes, if your app lets people create an account. Per Google's account deletion policy, you need two things: a clear path inside the app to request deletion of the account and its data, and a working web link where users can request deletion without reinstalling the app.
You can keep some data for fraud prevention or legal reasons, but you must say so in your privacy policy. Apps in healthcare or finance may need extra steps to complete a deletion.
How do I stop my app being rejected again?
Run a pre-submission check before every release. Save this list and tick it off with
whoever builds your app.
1. Open the release build (the file you upload), not a debug build, on a low-cost Android phone and use every screen.
2. Confirm the target API level is 36 or higher.
3. Add test login credentials and OTP instructions in App content.
4. Publish the privacy policy as a normal web page that names your app.
5. List every SDK in the app and match the Data safety form to it.
6. Remove every permission you cannot explain in one sentence to a user.
7. Add in-app account deletion and the web deletion link.
8. Check that screenshots, description, content rating and ads declaration match the uploaded build.
9. For digital sales inside the app, confirm Google Play Billing is used.
10. Keep the source code, keystore and Play Console access in your own account.
Item 10 matters more than it looks. If your developer holds the signing key and the account, a rejection can turn into a standoff. Our guide on how to write an app requirements document covers what to put in writing, and the post on first app mistakes Indian founders make lists the ownership traps.
How long does Play Store review take after I fix the issue?
Google does not publish one fixed time for app update reviews. The only figure on its testing page is that a production access application usually takes seven days or less. Plan your launch date with a buffer, and do not resubmit the same build several times, because that can slow you down.
FAQ (visible section at the end of the post, not counted in the word count)
Why was my app rejected by Google Play?
Google rejects an app when the build, the Data safety form or the store listing breaks a Play policy. The usual causes are a crash, a reviewer who cannot log in, a permission with no clear use, a privacy policy that does not match the app, and an old target API level. The message in Play Console names the policy.
How long does Google Play take to review an app after a rejection?
Google does not publish one fixed time for app update reviews. The only figure on its testing page is that a production access application usually takes seven days or less. Fix every issue in the message, resubmit once, and keep a buffer in your launch plan.
What is the target API level requirement for Google Play in 2026?
Since 31 August 2026, new apps and app updates must target Android 16 (API level 36). Existing apps must target Android 15 (API 35) to stay visible to new users on newer phones. Google offered extension requests until 1 November 2026.
Why was my Google Play production access rejected?
New personal developer accounts created after 13 November 2023 need a closed test with at least 12 testers, each opted in for 14 days in a row, before applying. A tester who opts out restarts their count. Recruit more than 12 people and keep them using the app.
Does my app need an account deletion option on Google Play?
Yes, if users can create an account in the app. You need a clear path inside the app to request deletion of the account and its data, plus a working web link for requests made without the app installed. You may keep some data for legal or fraud reasons if your privacy policy says so.
Can I use UPI or Razorpay inside my Android app?
For physical goods and real-world services, apps usually take payment through their own methods such as UPI. Digital content and subscriptions sold inside the app generally need Google Play Billing. Read Google's payments policy for your exact case before you launch.