eas-app-stores

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

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/sombek/fitness-guidance-app --skill eas-app-stores-sombek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eas-app-stores
Source: https://github.com/sombek/fitness-guidance-app/tree/main/mobile/.agents/skills/eas-app-stores
Command: npx skills add https://github.com/sombek/fitness-guidance-app --skill eas-app-stores-sombek

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 Store involves complex credential management, build configuration, version numbering, and store metadata. This Skill guides AI agents through the entire EAS build-and-submit pipeline so Expo apps reach production stores without manual portal work. ## Core Features & Use Cases - Production Builds & Submission: Run eas build and eas submit with production profiles for iOS and Android, including one-command TestFlight releases via npx testflight. - Store Configuration: Configure eas.json build and submit profiles, Apple App Store Connect API keys, Google Play service accounts, release tracks, and staged rollouts. - Metadata & ASO: Manage App Store listing metadata, keywords, localization, age ratings, and release strategy through EAS Metadata (store.config.json). - Use Case: A developer tags a v2.0 release and needs both platforms shipped. The Skill configures auto-incrementing version numbers, builds iOS and Android binaries, submits to TestFlight and the Play internal track, and pushes updated store metadata. ## Quick Start Ask the agent to build and submit your Expo app to TestFlight and the Google Play internal track using the production EAS profile.

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 use npx testflight for a quick TestFlight release. You need an Apple Developer account and an app record created in App Store Connect with a matching bundle ID.

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

Create a Google Cloud service account, link it in Play Console API access with release permissions, and add its JSON key path to eas.json under submit.production.android. Then run eas submit -p android --latest to push the build to your configured track.

Does EAS Metadata support Google Play Store listings?

No. EAS Metadata is currently in preview and supports the Apple App Store only. Google Play store listings, content ratings, and pricing must be configured manually in the Play Console.

Why does my submission fail with 'version code already used'?

Each upload requires a higher build number (iOS) or versionCode (Android). Set appVersionSource to remote and autoIncrement to true in eas.json so EAS increments these values automatically for every build.

What is the difference between TestFlight and App Store submission?

TestFlight distributes beta builds to up to 100 internal testers instantly or 10,000 external testers after a beta review, with builds expiring after 90 days. App Store submission requires full App Review before public release.

Can I automate store releases in CI/CD with EAS?

Yes. EAS Workflows let you define YAML pipelines that build and submit on tag pushes or pull requests. Use App Store Connect API keys instead of Apple ID authentication to avoid 2FA prompts in CI environments.