More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    EAS App Stores: Ship to the App Store and Google Play

    1

    Ship mobile releases with EAS — build profiles, signing, TestFlight and Play submissions, versioning, and store metadata, start to live.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    EAS App Stores: Ship to the App Store and Google Play

    EAS App Stores: Ship to the App Store and Google Play

    Example session with this skill installed

    Ship our Expo app's first production release, version 1.0.0, to the App Store and Google Play with EAS. Walk me through it.

    • Read your context and instructions
    • Compiled the eas app stores

    First production release shipped. Config: eas.json with development, preview, and production profiles; bundle identifiers preserved. Version: 1.0.0, build 1, recorded with the release scope. Build: production profile clean on first run; build ID recorded. Beta: TestFlight internal testers found two issues (stale screenshot flow, crash on an older device) — fixed in build 2. Metadata: description, keywords, screenshots reviewed against build 2. Submit: build 2 to TestFlight and Play Console, receipts recorded. Review: Apple passed in two days, Play in one. Listing live with version, build, receipts, and beta fixes recorded. The release record holds everything needed to repeat or debug the release: version 1.0.0, build 2, the build ID, the production profile, EAS-managed signing, both submission receipts, the two beta issues and their fixes, and the metadata review. The review window was communicated to stakeholders as an estimate — two days for Apple, one for Play — never as a promise, and both stores landed inside it. The rejection log is empty for this release, and the beta process that caught the two issues is now the standing path for every future release. Rubric score: 8/8.

    eas.json

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

    About this skill

    EAS (Expo Application Services) is a cloud build-and-submit pipeline: it compiles your app on hosted infrastructure and can deliver the binary to Apple and Google for you. This skill covers the full path from eas.json to a live listing: configuring the project and build profiles, versioning deliberately, building, submitting to TestFlight and Play Console, beta testing before production, preparing store metadata, running it in CI, handling rejections, and covering native apps without Expo. It states the honest limits up front: EAS cloud builds consume plan resources, Apple Developer and Google Play memberships are separate paid programs, and a successful build or a queued submission is not an acceptance — Apple review, TestFlight processing, and Play review are separate gates with their own clocks. A worked example ships a first production release end to end, from version bump to store listing.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.

    A successful build or queued submission is not an acceptance — review is a separate gate with its own clock.

    • Store memberships are separate paid programs; check current pricing before promising timelines.
    • Cloud builds consume plan resources, including failed builds.

    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 buying a skill.

    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

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    It varies by store and by queue — Apple and Google set the clock, not you. Record the submission receipt and communicate the window as an estimate, never as a promise.

    Either approach works, but pick one and stick with it for the release. Mixing EAS-managed and self-managed signing mid-release is how credential conflicts happen.

    Yes. A build passing proves it compiles; a beta proves it works for real users on real devices. Beta issues are the cheapest fixes you will ever get.

    New in Mobile Development