Submit to Google Play
Prepare the signed AAB, testing tracks, Data safety, deletion, billing, and rollout.
Google Play submission uses a production Android App Bundle and normally moves through an internal or closed testing track before production.
Prompt
Read agent-skills/submit-android.md, STORE-READINESS.md, and the current Play
Console requirements shown for my account. Prepare the signed production AAB,
internal test, Data safety, deletion, billing, listing, and app-access details.
Stop before promoting a track or submitting until I approve the release and
rollout percentage.Verify the real console state
Account testing requirements can vary by account type and can change. Follow the requirements displayed in the actual Play Console rather than an old tutorial.
Complete Data safety from observed behavior, including health-related data, AI/photo/audio processing, analytics, diagnostics, encryption, and deletion. Installed SDK names do not answer the form for you.
Android-specific pass
Test notification permission on current Android, predictive back, edge-to-edge, camera/photo picker, dark mode, low-memory restore, billing testers, restore, deep links, and the public deletion URL. Confirm package name, app signing, version code, target SDK requirement, content rating, audience, privacy/support URLs, screenshots, feature graphic, and reviewer access before rollout.