expo-deployment

Deploy Expo apps to iOS App Store, Google Play, and web hosting using EAS.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Divith123/Flamingo --skill expo-deployment-divith123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: expo-deployment
Source: https://github.com/Divith123/Flamingo/tree/main/.agents/skills/expo-deployment
Command: npx skills add https://github.com/Divith123/Flamingo --skill expo-deployment-divith123

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Shipping a React Native app to the App Store, Google Play, and web involves juggling credentials, build profiles, store metadata, and CI/CD pipelines. This Skill consolidates the entire Expo Application Services (EAS) deployment workflow into one reference so you can build, submit, and automate releases without hunting through documentation. ## Core Features & Use Cases - Store Submission: Build and submit production binaries to the iOS App Store, TestFlight, and Google Play tracks (internal, alpha, beta, production) with single EAS CLI commands. - App Store Metadata & ASO: Manage titles, keywords, descriptions, age ratings, and localized listings via store.config.json and eas metadata:push. - CI/CD Automation: Use EAS Workflows to trigger builds on push, deploy web previews for pull requests, and automate full release pipelines on version tags. - Use Case: You have finished your Expo app and need to ship it. Run npx testflight to get a beta build to testers, then use the release workflow to build and submit to both stores automatically when you push a v* tag. ## Quick Start Install the EAS CLI, run eas init to generate eas.json, then build and submit a production iOS build with eas build -p ios --profile production --submit.

Frequently Asked Questions about expo-deployment

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?▼

Run eas build -p ios --profile production --submit to build and submit in one step. You need an Apple Developer account, an app record in App Store Connect, and credentials configured via eas credentials or an App Store Connect API key.

How do I submit an Expo build to TestFlight?▼

Run npx testflight to build and submit to TestFlight in one command. Set EXPO_APPLE_ID and EXPO_APPLE_TEAM_ID environment variables to skip interactive prompts on subsequent runs.

How do I set up Google Play Store submission with EAS?▼

Create a service account in Google Cloud Console, link it in Play Console API access with release permissions, and reference the JSON key via serviceAccountKeyPath in eas.json. Then run eas submit -p android with your chosen track.

Does EAS support staged rollouts on Google Play?▼

Yes. Set releaseStatus to inProgress and specify a rollout fraction like 0.1 in the android submit configuration of eas.json. You can increase the percentage later via Play Console or subsequent submissions.

Why does my EAS submission fail with version code already used?▼

Each upload requires a higher versionCode on Android or build number on iOS. Enable autoIncrement: true in your eas.json build profile and set appVersionSource to remote so EAS manages version numbers automatically.

Can I automate Expo deployments in CI/CD?▼

Yes. EAS Workflows let you define YAML files in .eas/workflows that trigger builds, submissions, OTA updates, and web deploys on push, pull request, tags, or schedules. Store secrets like service account keys in EAS Secrets rather than workflow files.