eas-app-stores

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

16|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/AIBiz-Automatyzacje/workspace-template-mobile --skill eas-app-stores-aibiz-automatyzacje
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eas-app-stores
Source: https://github.com/AIBiz-Automatyzacje/workspace-template-mobile/tree/main/.claude/skills/eas-app-stores
Command: npx skills add https://github.com/AIBiz-Automatyzacje/workspace-template-mobile --skill eas-app-stores-aibiz-automatyzacje

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Releasing a mobile app to the App Store and Google Play involves complex credential setup, version management, and store-specific submission rules. This Skill guides the entire EAS build and submit pipeline so releases ship without manual portal work. ## Core Features & Use Cases - Store Builds & Submission: Run eas build and eas submit for iOS App Store, Google Play, and TestFlight with production profiles in eas.json. - Version & Credential Management: Automatic build number increments via appVersionSource: "remote", plus Apple API keys and Google service account setup. - Store Metadata & ASO: Manage App Store listings, keywords, localization, and release strategy through EAS Metadata (store.config.json). - Use Case: You finished a feature and want to release it. The Skill builds production binaries for both platforms, submits iOS to TestFlight and Android to the internal track, and pushes updated store metadata in one flow. ## Quick Start Ask the assistant to build the app with EAS production profile and submit it to TestFlight and the Google Play internal track.

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 in one step, or `eas submit -p ios --latest` for an existing build. Configure your Apple ID and ascAppId in the submit section of eas.json first.

How do I submit an Android build to Google Play using EAS?

Create a service account in Google Cloud, link it in Play Console API access, and set `serviceAccountKeyPath` in eas.json. Then run `eas submit -p android --latest` to upload to your configured track.

Does EAS support TestFlight beta testing?

Yes, running `npx testflight` builds and submits directly to TestFlight. Internal testers get builds instantly, while external testers require a one-time Beta App Review before receiving updates.

Why does my submission fail with version code already used?

Each upload requires a higher build number or versionCode. Set `autoIncrement: true` in your eas.json production profile and `appVersionSource: "remote"` so EAS manages version numbers automatically.

Can I manage App Store metadata and keywords from code?

Yes, EAS Metadata uses a store.config.json file to manage titles, keywords, descriptions, localization, and release strategy. Pull existing data with `eas metadata:pull` and push updates with `eas metadata:push`.

What are the costs and account requirements for EAS store submission?

EAS build and submit consume plan build minutes under Expo's paid tiers with free limits. Store submission additionally requires a paid Apple Developer account and a Google Play Console account.