eas-app-stores

Build and submit iOS and Android apps to TestFlight, the App Store, and Google Play with EAS.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Releasing mobile apps to the Apple App Store and Google Play involves complex signing, versioning, submission, and review steps. This Skill guides the full EAS build-and-submit pipeline so releases reach TestFlight, the App Store, and Google Play without manual portal guesswork. ## Core Features & Use Cases - EAS Build & Submit Pipelines: Configure eas.json profiles, run production builds, and submit binaries to App Store Connect and Google Play with auto-submit or explicit build IDs. - Store-Specific Guidance: Detailed references for TestFlight beta testing, iOS App Store review and release, Google Play tracks and staged rollouts, and App Store metadata/ASO via store.config.json. - Native iOS Support: Covers SwiftUI/UIKit apps without a React Native runtime, including archive verification, CFBundleVersion troubleshooting, and icon alpha-channel checks. - Use Case: A team with an Expo app needs its first production release. Use this Skill to configure eas.json, build for both platforms, submit to TestFlight and the Play internal track, then complete App Review and a staged rollout. ## Quick Start Use the eas-app-stores skill to configure eas.json and build and submit my app to TestFlight and Google Play.

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 iOS app to TestFlight with EAS?▼

Run eas build with a store-distribution iOS profile, then eas submit with the explicit build ID. For Expo or React Native apps, npx testflight provides a quick combined flow. Verify tester availability in App Store Connect after Apple processing completes.

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

Create a Google Cloud service account, link it in Play Console API access, and reference its JSON key in the android submit profile of eas.json. Then run eas submit -p android to upload an AAB to the configured track such as internal or production.

Can EAS build a native Swift app without React Native?▼

Yes, EAS Build supports SwiftUI/UIKit projects with no Expo or React Native runtime. Keep the checked-in Xcode project as source of truth, provide a minimal app.json and Podfile, and select the shared scheme in the build profile.

Why does my App Store upload fail with a duplicate build number?▼

The archive's CFBundleVersion must increment for each upload. Inspect the built app's Info.plist with plutil; for native Swift projects, a generated plist with a fixed CURRENT_PROJECT_VERSION can keep every archive at build 1 despite EAS auto-increment.

Does EAS Metadata support Google Play listing management?▼

No, EAS Metadata is currently in preview for the Apple App Store only. It manages store.config.json for titles, keywords, and release settings; Google Play listings are configured in Play Console.

Why is my TestFlight build not available to testers after upload?▼

A successful EAS upload does not grant tester access. Apple processing, export-compliance declarations, and group assignment in App Store Connect all affect availability; check the build's TestFlight state with eas submit:status.