eas-app-stores

Build and submit Expo apps to the App Store, Google Play, and TestFlight using EAS.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/gmackie/agent-skills --skill eas-app-stores-gmackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eas-app-stores
Source: https://github.com/gmackie/agent-skills/tree/main/skills/eas-app-stores
Command: npx skills add https://github.com/gmackie/agent-skills --skill eas-app-stores-gmackie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires eas-cli, and includes references (resource) components.

What problem does it solve? Releasing a mobile app to the iOS App Store and Google Play involves complex credential management, version numbering, store metadata, and submission tooling. This Skill guides the full EAS build-and-submit pipeline so Expo apps reach production stores without manual portal work. ## Core Features & Use Cases - Store Builds & Submissions: Run eas build and eas submit with production profiles for iOS App Store, Google Play, and TestFlight. - Configuration Management: Set up eas.json build and submit profiles, remote version source, auto-incrementing build numbers, and store credentials. - Metadata & ASO: Manage App Store listing metadata, keywords, localization, and release strategy via EAS Metadata and store.config.json. - Use Case: You are ready to ship your Expo app. Use this Skill to configure eas.json, produce production builds for both platforms, submit to TestFlight for beta testing, and push localized store metadata before release. ## Quick Start Ask the assistant to build and submit your Expo app to TestFlight and the Google Play internal track using EAS production profiles.

Frequently Asked Questions about eas-app-stores

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit an Expo app to the App Store with EAS?▼

Run eas build -p ios --profile production --submit to build and submit to App Store Connect in one step. Configure your Apple credentials and ascAppId in the submit section of eas.json first, or use npx testflight for quick TestFlight submissions.

How to set up Google Play submission for an Expo app?▼

Create a service account in Google Cloud Console, link it in Play Console API access with release permissions, and add serviceAccountKeyPath to the android submit profile in eas.json. Then run eas submit -p android --latest to upload your build.

Does EAS handle version and build numbers automatically?▼

Yes. Set appVersionSource to remote and autoIncrement to true in eas.json, and EAS manages build numbers and Android version codes for every upload. You can inspect or override values with eas build:version:get and eas build:version:set.

Why does EAS submit fail with version code already used?▼

Google Play rejects uploads when the versionCode was used in a previous release. Enable autoIncrement in your eas.json production build profile so EAS increments the version code automatically for each submission.

Can I manage App Store metadata and ASO from the command line?▼

Yes, EAS Metadata uses a store.config.json file to manage titles, subtitles, keywords, localization, age ratings, and release strategy. Pull existing metadata with eas metadata:pull and push updates with eas metadata:push after submitting a binary.

What are the costs and account requirements for EAS store deployment?▼

EAS build and submit consume plan build minutes under Expo Application Services pricing, which has free-tier limits. Store submission additionally requires a paid Apple Developer account and a Google Play Console account.