Key takeaways
- Work through Play Console in its own order: build, App content, store listing, testing, release.
- The merged manifest of the release bundle – not your source manifest – shows the permissions Google sees.
- Every declaration under App content must match the code: Data safety, ads, app access, account deletion, sensitive permissions.
- New personal developer accounts need a 14-day closed test with at least 12 testers before production access.
- Treat the pre-launch report as a free extra tester and turn its findings into agent tasks.
Why Play review needs its own checklist
On the App Store, a reviewer mostly tests the app. On Google Play, much of the review is a comparison: does the App Bundle do what your declarations in Play Console say it does? Automated checks read the target API level, the permissions in the merged manifest and the SDKs you ship; policy reviewers compare your Data safety answers, ads declaration and store listing with the app itself.
Agent-built apps fail that comparison easily. Their dependencies and permissions grow with every prompt – a plugin here, an analytics package there – while the declarations were filled in once, months ago. The remedy is a division of labour: the agent produces the facts from the code, the account holder makes the declarations. The sections below follow Play Console's order.
1. The build: what the agent verifies from the repository
| Check | Ask the agent to | Background |
|---|---|---|
| Target API level | Confirm the release variant targets Android 16 (API level 36) | Target API guide |
| App Bundle and signing | Build an .aab with release signing from environment variables; confirm no keystore is in the repository | Play App Signing holds the app key; you keep the upload key |
| versionCode | Confirm it is higher than every build already uploaded | Uploads with a used code are refused |
| Permissions | List every permission in the merged manifest and the library that added it | Sensitive permissions |
| Location in the background | Flag background location and name the feature that needs it | Background location |
| Advertising ID | Report whether the AD_ID permission is present and which SDK adds it | Must match the Advertising ID declaration |
| SDKs | List the release dependency tree, including transitive analytics, ads and crash SDKs | Input for Data safety |
| Release behaviour | Confirm release builds use production servers and contain no debug tooling | Broken functionality |
Two commands worth naming in the prompt: ./gradlew :app:dependencies --configuration releaseRuntimeClasspath for the dependency tree, and bundletool dump manifest on the built bundle for the permissions Google will actually see. For Expo, Flutter or Capacitor projects, point the agent at the generated Android project – plugins add native SDKs and permissions that never appear in JavaScript or Dart.
Talk to an AI Code Engineer about getting your AI-built app through Play review.
In a free call we look at what you built, tell you honestly what stands between it and an approved release – and whether you need us at all.
2. App content: declarations the account holder makes
Under Policy and programs → App content (labels move occasionally), Play Console collects declarations that must match the build. Use the agent's report from step 1 as evidence for each one:
- Privacy policy. A public HTTPS page, also linked inside the app.
- App access. Working credentials and instructions for every login-gated area, without one-time codes.
- Ads. Whether the app shows ads – including ads delivered through an SDK you added for something else.
- Content rating. The questionnaire answered for everything the app can display, including user-generated and AI-generated content.
- Target audience. The age groups; including children brings in the Families requirements.
- Data safety. Every data type the app and its SDKs send off the device; see our Data safety playbook.
- Account deletion. If users can create accounts, an in-app path and a web link for deletion requests; see the account deletion guide.
- Further declarations such as the Advertising ID, financial features or health, wherever they apply to your app.
The agent should never fill these in on its own, even where a browser-controlling tool would make that possible. Each answer is a statement the developer account makes to Google.
3. Store listing: drafted with AI, checked by a person
AI writing tools produce listing copy fast, and they reach for exactly the words the Metadata policy rejects: "best", "#1" or "free" in the title, emojis, keyword lists, testimonials without a source. Before publishing, confirm that:
- the title has 30 characters or fewer and reads like a name, not a row of search terms,
- screenshots come from the Android build – no iPhone frames, App Store badges or award ribbons,
- icon and feature graphic carry no ranking, price or promotional claims,
- the full description promises only features that ship in this release,
- every translation got the same check.
Details are in our guide to the Metadata policy. If the app mainly displays a website, also read the WebView spam policy guide before you submit.
4. Testing: closed test and pre-launch report
If your developer account is a personal account created after November 13, 2023, production access requires a closed test with at least 12 testers opted in for 14 consecutive days. Plan it as a small project rather than a formality; our closed testing playbook shows where an agent helps and where it must not.
Every build on a testing track also gets a pre-launch report: Google installs it on a range of test devices, explores it automatically and reports crashes, ANRs, accessibility issues and security warnings. Copy each finding into an issue for the agent, with device and Android version. A crash in the pre-launch report is a crash the reviewer can run into as well.
5. Release: deliberate and reversible
For the first production release, a person sends the release for review. For updates, a staged rollout lets a problem the review missed reach a fraction of users first. The agent's role at this stage is narrow: draft release notes from the merged pull requests, and confirm that the versionCode, target API level, permissions and SDK list have not drifted since you last reviewed the declarations. That kind of drift is a typical reason why an update gets rejected although the first version was approved.
Our AI Code Engineers take Android apps through this whole sequence in your own Play Console – signing, declarations, closed test planning and the review itself – as part of the Android submission service. The iOS version of this list is the App Store review checklist for AI-built apps.
Google Play pre-submission checklist
- The release App Bundle targets API level 36 and is signed with the upload key from CI secrets.
- The versionCode is higher than any build already on Play.
- The agent listed every permission in the merged manifest and every SDK in the release dependency tree.
- Sensitive and background permissions are either removed or tied to a declared core feature.
- Data safety answers, the ads declaration and the Advertising ID declaration match the build.
- Apps with accounts offer in-app deletion and a web link for deletion requests.
- Reviewer credentials work on a clean device without one-time codes.
- Content rating and target audience reflect everything the app can show.
- Title, icon, screenshots and descriptions follow the Metadata policy in every language.
- New personal accounts completed the 12-tester, 14-day closed test.
- The latest pre-launch report shows no crashes or ANRs.
Frequently asked questions
Can a coding agent fill in the Play Console declarations?
It should prepare them, not submit them. The agent can produce a report of permissions, SDKs and data flows and even draft answers, but the account holder reviews and enters every declaration, because Google holds the developer responsible for their accuracy.
Why does Play see permissions I never added?
Libraries and plugins declare permissions in their own manifests, and Gradle merges them into your app. Check the merged manifest of the release bundle, remove what you do not need with a manifest removal rule, and test the affected features afterwards.
Do organization accounts also need the closed test?
Google documents the 12-tester, 14-day requirement for personal accounts created after November 13, 2023. Organization accounts are not covered by it, but every release on any account still goes through Play review.
Can you take our app through Play review?
Yes. Book a free call and an AI Code Engineer looks at your build and Play Console with you. We can handle signing, declarations, testing tracks and the review in your own account.
Free, 15 minutes, no obligation
Get your app from agent output to approved release.
Our AI Code Engineers take apps built with Claude Code, Codex, Cursor, Lovable, Base44 and co. through signing, CI/CD, store listings and review – in your own developer accounts.
AI tools, store policies and requirements change quickly – always check the current documentation of the tools and stores you use. This article is independent advice and not affiliated with or endorsed by Apple, Google, Anthropic, OpenAI or any other company or product mentioned; all trademarks belong to their owners.