Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Google Play Release Guide (Flutter & React Native)

    1

    Get a Flutter, React Native or Expo app onto Google Play: the declarations in the order Play wants them, an .aab preflight, and which steps only a human can do.

    Free

    1 useSecurity scanned
    Google Play Release Guide (Flutter & React Native)

    Google Play Release Guide (Flutter & React Native)

    Example session with this skill installed

    Get this app ready for its first Google Play release.

    • Read your context and instructions
    • Compiled the google play release

    What I ran

    The preflight, on an app that hadn't been built yet:

    Bundle
      FAIL  no bundle at build/app/outputs/bundle/release/app-release.aab — build one first (flutter build appbundle)
    
    Nothing else can be checked without it.
    

    What it means

    It stops at the first thing that makes everything else uncheckable. With no .aab there's nothing to check for signing key, target SDK or the AD_ID permission, so it says so instead of passing.

    Next steps

    1. flutter build appbundle --release, then run it again.
    2. The second run checks the signing key (not the debug key Gradle falls back to in silence), target SDK, AD_ID against your declaration, store text and image limits, the privacy policy URL and EEA consent.
    3. Do the Play Console declarations in the order SKILL.md gives. The first upload is yours; handoff.sh opens the folder and the console page for it.

    Output is from a real run.

    3. Do the Play Console declarations in the order SKILL.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The Play Console has a setup checklist that won't finish if you do things in the wrong order, and a "Send for review" button that stays grey without saying why. This skill lays out the order: data safety, content rating, target audience, the advertising ID declaration, ads, and the health, financial and government declarations.

    It works on Flutter, React Native and Expo projects and detects which one it is looking at. For React Native and Expo it also reads the package name and versionCode from build.gradle or app.json, flags a release build signed with the debug key (or notes that EAS Build signs for you), catches an EAS production profile that builds an APK instead of an app bundle, and checks for the consent calls from react-native-google-mobile-ads.

    Before you upload, a preflight checks the signed .aab: is it signed with your upload key and not the debug key, is the target SDK current, does the advertising ID permission match what you declared, do the store text and images fit Play's limits, is there a privacy policy, and is there an EEA ad consent message if you serve ads in Europe.

    It's honest about the steps it can't do: the first bundle upload is yours, and it tells you exactly when.

    Scripts: preflight.sh, handoff.sh (macOS only; --dry-run shows what it would open).

    These are free and MIT-licensed, and the source is at github.com/jameskrupnik/indie-app-skills. If you ship several apps, my paid skills cover the rest of the release: new-app (forking without carrying the parent's Firebase and ad ids), ship-ios (fork to App Store review), bug-hunt and daily-update (pacing releases across many apps).

    Only tested in Claude Code. The preflight can't tell which build flavor or --dart-define produced the bundle. handoff.sh is macOS only. The target SDK check needs bundletool.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Requires

    expo
    Node.js

    Permissions

    Terminal / Shell
    Network Access
    Read Files

    File Scopes

    your
    project/**

    Reads your project and the built .aab and runs bash. The preflight requests your privacy policy URL to check it resolves (skip with --offline). handoff.sh opens Finder and your browser on macOS. Nothing is uploaded.

    Listed1 month ago
    Updated1 month ago

    What's inside

    Frequently Asked Questions

    This skill solves the 'greyed-out button' problem by providing the specific sequence for declarations (like Data Safety and Advertising ID) that the Play Console requires before allowing a release.

    The `preflight.sh` script verifies that your signed .aab matches your console declarations, checking critical details like the target SDK version, privacy policy links, and EEA consent requirements.

    The included scripts are designed for macOS; however, the strategic guidance and sequencing for the Play Console declarations are applicable to developers on any operating system.

    Due to security and account permissions, you must perform the initial bundle upload manually; this skill tells you exactly when to do so to ensure the rest of the automated flow stays synced.

    This is a free, MIT-licensed utility focused on the final release stage; the creator offers paid companion skills for forking apps, iOS shipping, and multi-app maintenance.

    New in Mobile Development