Google Play rejected your app. Here's what it means.

How a Google Play rejection works

When Google rejects an app, you get an email and a notice in Google Play Console under the app's policy status. The message names the policy, sometimes with a screenshot of where the reviewer found the problem. A rejection only stops that release: if an older version of your app is already live, it stays live.

Google uses three words that are easy to mix up:

• Rejected — this release won't be published. Fix it and resubmit. No mark against your account.
• Removed — a live app was taken down for a policy problem. Fix it and resubmit; the listing comes back when approved.
• Suspended — the app is gone and counts as a strike. Repeated or serious violations can lead to your developer account being terminated.

Almost everything we see on AI-built apps is in the first group.

The rejections and blockers we see most

• The closed testing rule (12 testers, 14 days)Not a rejection, but it stops more new apps than any policy. Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in continuously for 14 days, then apply for production access. Until then, production is switched off.
• Data safety form doesn't match the appEvery app must declare what it collects and shares. AI-built apps usually collect email, usage and crash data through their backend and analytics, while the form says "no data collected".
• Target API level too lowGoogle requires new apps and updates to target a recent Android version and raises the bar every year. Builder exports and wrappers often target an older one and get rejected on upload.
• Wrong file format ("App Bundle")New apps have had to be published as an Android App Bundle since 2021. Uploading the older APK format is refused outright.
• Deceptive behavior and misleading claimsA title, description or screenshots that promise things the app doesn't do, or an app that doesn't match its listing. AI-written store listings are the usual cause.
• No login details for the reviewerIf any part of the app is behind a login, Google needs working sign-in details on the app's content page. Without them the reviewer can't get in, and the app is usually rejected.
• User data: privacy policy and account deletionA privacy policy link in the listing and in the app, and a way to delete an account for apps with sign-up, are required here too.
• Apps that add nothingGoogle is more relaxed about web views than Apple, but its spam and minimum functionality policy still rejects apps that barely work, crash, or mostly send people to a website. Apple's version is Guideline 4.2.

What Google is actually asking for

"Developers with personal accounts created after November 13, 2023, must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days."Google Play Console Help, app testing requirements — support.google.com

Across all of its policies, Google's intent is the same: an app that is honest about what it does and what it collects, built for a current Android version, tested by real people before the public sees it, and reviewable by a stranger. The testing rule exists because too many first apps were broken or abandoned; the Data safety and Deceptive behavior policies exist because listings lied. None of it is aimed at AI-built apps in particular, but AI-built apps hit all of it at once.

Two things about timing are worth knowing. Google says its review of a production access application usually takes a week or less. And the 14 days have to be continuous: testers who leave the test early don't count toward the 12.

What we fix

We go through your Google Play Console the way a reviewer does, from the policy declarations to the build itself, and fix everything at once rather than one rejection at a time. The usual issues:

Everything happens inside your own Google Play Console, through an invite with only the permissions we need. The release goes out from your account. One thing we can't do is be your twelve testers: those have to be real people who install your app. We make sure the test is set up right and that the app passes policy while it runs.

How long it takes

Google's own review is usually a few days, but can be up to a week or longer for new accounts. If the closed testing rule applies to you, add at least 14 days for the test and up to a week for the production access decision.

1. Day 0
   You share your project and the rejectionA share link or invite from your builder, plus an invite to your Google Play Console.
2. Day 1
   We review the app and the consoleYou get a plain-English plan listing every policy issue we found, not only the one Google named.
3. Days 1–4
   We make the changesBuild, declarations and listing. Most are done within a few days.
4. Then
   Released from your accountGoogle reviews it again, usually within a few days. New accounts can take longer.
5. Done
   Approved, or we go againUnlimited resubmissions are included. Full refund if it is never approved.

What happens if you ignore it

A rejected release just sits there. A removed app stays down. Neither hurts your account by itself. What does hurt is repeating the same violation after Google has pointed it out: Google's policies say repeated or serious violations can lead to suspension of the app and, eventually, termination of the developer account, and terminated accounts don't easily come back.

Policy requirements also change on a schedule. The target Android version goes up every year, and the Data safety and account deletion rules were both added after many apps were already live. An app you ignore today can be blocked from updates tomorrow.

Submitting to both stores?

Most of what Google asks for has an Apple twin. If you're fixing both, tell us when you start your order.

Built with an AI tool?

Each builder has its own patterns. See what we usually find for yours:

Questions about Google Play rejections