Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    EAS Build & Submit Doctor

    1

    Two jobs: get a correct pipeline from code to TestFlight and Play Console, and get a red build green quickly.

    Free

    Security scanned
    EAS Build & Submit Doctor

    EAS Build & Submit Doctor

    Example session with this skill installed

    eas submit keeps failing for android, first time publishing this app. log says:

    Google Api Error: Invalid request - Only releases with status draft may be created on draft app.

    my eas.json submit profile has track production and releaseStatus completed. help

    • Read your context and instructions
    • Compiled the eas build

    The Play Console app is still a

    draft. That happens on every new app until its first release is live, and while the app is a draft Google only accepts releases with status draft. Asking for releaseStatus: "completed" is exactly what that error rejects.

    Fix

    The eas.json in this repo has an empty submit profile ("production": {}), not the track: production / completed setup you described. Your real config may be uncommitted or in a different file. Either way, set it to:

    "submit": {
      "production": {
        "android": {
          "track": "internal",
          "releaseStatus": "draft"
        }
      }
    }
    

    Then resubmit the build you already have. You don't need to rebuild just for this error:

    npx eas-cli@latest submit -p android --latest
    

    Then, in Play Console

    1. Fill in every required section on the app's Dashboard: store listing, content rating, target audience, Data safety, App access, ads declaration. Until they're done, the app stays a draft.
    2. Open the draft release that EAS uploaded and roll it out from there by hand. Once the first release is live, the app is no longer a draft.
    3. After that, you can switch releaseStatus to completed. For production, a staged rollout ("inProgress" with "rollout": 0.1) is safer than going straight to 100%.

    If your developer account is a personal one created after 13 Nov 2023: Google won't give you production access until you've run a closed test with at least 12 testers opted in for 14 days in a row. So go internal → closed testing (alpha) → production. Submitting straight to production will keep failing until then.

    A separate problem in your eas.json

    The production

    build profile has "developmentClient": true. That makes your store build a development client, not your real app. Unless you meant to do that, remove that line and rebuild before anything goes to real users:

    "production": {
      "autoIncrement": true
    }
    

    That means the build you're submitting now is probably a dev-client build. It's fine to submit it as a draft just to get past this error, but don't roll it out to users.

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

    About this skill

    Two jobs: get a correct pipeline from code to TestFlight and Play Console, and get a red build green quickly.

    What it does

    • Build log diagnosis (scripts/diagnose-build-log.mjs, zero-dependency Node 18+): matches about 30 known EAS Build and Submit failures — CocoaPods, signing and provisioning, Gradle, JS bundling, out-of-memory, ITMS upload errors, "Only releases with status draft", reused versionCode / buildNumber, npm ci lockfile errors and more. Reports them earliest-first (the first failure is usually the real one) with the cause, the fix and whether you need a rebuild.
    • Config check (scripts/check-eas-config.mjs): validates eas.json build and submit profiles and the files they point to, committed credentials, rollouts and workflows.
    • References: an annotated eas.json, App Store Connect API key and Google Play service account setup, staged rollouts, and EAS Workflows CI examples.

    Output

    The failure, why it happened, the exact fix (eas.json key, Play Console step or command) and the next step: resubmit the same build or rebuild. Both scripts print a human report or --json and exit non-zero on problems, so they work in CI too.

    Freshness

    Checked against the EAS docs, Expo SDK 58 and Google Play Console Help on 29 Oct 2026.

    Open source (MIT): https://github.com/disconnectuss/expo-ship-kit.skills. Part of expo-ship-kit.

    Log diagnosis matches known patterns; a failure it hasn't seen falls back to the first error-looking lines, which the agent then reads with you. It can't access your EAS account, Apple Developer or Play Console, so credential and console-side fixes are steps for you to do. Node.js 18+ for the scripts.

    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

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 day ago

    • Free with an Agensi account

    Requires

    Node.js
    expo
    expo-doctor

    Permissions

    Terminal / Shell
    Read Files

    Terminal: runs `node scripts/diagnose-build-log.mjs <log file>` and `node scripts/check-eas-config.mjs`; the latter calls `git ls-files` / `git check-ignore` to see whether credential files are committed. Read Files: the build log you point it at, eas.json and .eas/workflows/*.yml. Credential files are only checked for existence and git status, never read. No network calls. Nothing is sent anywhere.

    Listed1 day ago

    What's inside

    Frequently Asked Questions

    This skill automates the debugging of cryptic mobile build logs (Xcode/Gradle) and provides validated EAS configuration templates, saving hours of manual troubleshooting and preventing 'trial-and-error' build attempts that consume EAS credits.

    Node.js 18+ for the scripts and any agent that reads SKILL.md. The EAS CLI is only needed to run the commands the skill suggests (eas build, eas submit, eas credentials).

    SKILL.md, two zero-dependency Node 18+ scripts (diagnose-build-log.mjs and check-eas-config.mjs) and four references: build-errors.md, eas-json.md (an annotated eas.json), submit.md (App Store Connect and Google Play setup) and workflows.md (EAS Workflows CI). It's free and MIT-licensed; the same files are on GitHub.

    Yes for diagnosis: the log matcher recognises common signing and provisioning failures (like a profile missing a new capability) and explains the fix. check-eas-config also flags the App Store Connect API key (.p8) and Google service account JSON that eas.json points to when they're committed to git or not gitignored. The fix itself usually runs through `eas credentials`, which you run with your own Apple / Google access.

    Yes. The log patterns cover the native phases (CocoaPods, Xcode, Gradle) that both run on EAS. For bare projects with committed ios/ and android/ folders, remember that app.json changes don't reach those folders; the skill points that out when it matters.

    New in Mobile Development