| name | expo-deployment |
| description | Deploying Expo apps to iOS App Store, Android Play Store, web hosting, and API routes |
| version | 1.0.0 |
| license | MIT |
Deployment
This skill covers deploying Expo applications across all platforms using EAS (Expo Application Services).
References
Consult these resources as needed:
- ./references/workflows.md -- CI/CD workflows for automated deployments and PR previews
- ./references/testflight.md -- Submitting iOS builds to TestFlight for beta testing
- ./references/app-store-metadata.md -- Managing App Store metadata and ASO optimization
- ./references/play-store.md -- Submitting Android builds to Google Play Store
- ./references/ios-app-store.md -- iOS App Store submission and review process
Quick Start
Install EAS CLI
npm install -g eas-cli
eas login
Initialize EAS
npx eas-cli@latest init
This creates eas.json with build profiles.
Build Commands
Production Builds
npx eas-cli@latest build -p ios --profile production
npx eas-cli@latest build -p android --profile production
npx eas-cli@latest build --profile production
Submit to Stores
npx eas-cli@latest build -p ios --profile production --submit
npx eas-cli@latest build -p android --profile production --submit
npx testflight
Web Deployment
Deploy web apps using EAS Hosting:
npx expo export -p web
npx eas-cli@latest deploy --prod
npx eas-cli@latest deploy
EAS Configuration
Standard eas.json for production deployments:
{
"cli": {
"version": ">= 16.0.1",
"appVersionSource": "remote"
},
"build": {
"production": {
"autoIncrement": true,
"ios": {
"resourceClass": "m-medium"
}
},
"development": {
"developmentClient": true,
"distribution": "internal"
}
},
"submit": {
"production": {
"ios": {
"appleId":
Platform-Specific Guides
iOS
- Use
npx testflight for quick TestFlight submissions
- Configure Apple credentials via
eas credentials
- See ./reference/testflight.md for credential setup
- See ./reference/ios-app-store.md for App Store submission
Android
- Set up Google Play Console service account
- Configure tracks: internal → closed → open → production
- See ./reference/play-store.md for detailed setup
Web
- EAS Hosting provides preview URLs for PRs
- Production deploys to your custom domain
- See ./reference/workflows.md for CI/CD automation
Automated Deployments
Use EAS Workflows for CI/CD:
name: Release
on:
push:
branches: [main]
jobs:
build-ios:
type: build
params:
platform: ios
profile: production
submit-ios:
type: submit
needs: [build-ios]
params:
platform: ios
profile: production
See ./reference/workflows.md for more workflow examples.
Version Management
EAS manages version numbers automatically with appVersionSource: "remote":
eas build:version:get
eas build:version:set -p ios --build-number 42
Monitoring
eas build:list
eas build:view
eas submit:list
Expo Deployment
Overview
Deploy Expo applications to production environments, including app stores and over-the-air updates.
When to Use This Skill
Use this skill when you need to deploy Expo apps to production.
Use this skill when:
- Deploying Expo apps to production
- Publishing to app stores (iOS App Store, Google Play)
- Setting up over-the-air (OTA) updates
- Configuring production build settings
- Managing release channels and versions
Instructions
This skill provides guidance for deploying Expo apps:
- Build Configuration: Set up production build settings
- App Store Submission: Prepare and submit to app stores
- OTA Updates: Configure over-the-air update channels
- Release Management: Manage versions and release channels
- Production Optimization: Optimize apps for production
Deployment Workflow
Pre-Deployment
- Ensure all tests pass
- Update version numbers
- Configure production environment variables
- Review and optimize app bundle size
- Test production builds locally
App Store Deployment
- Build production binaries (iOS/Android)
- Configure app store metadata
- Submit to App Store Connect / Google Play Console
- Manage app store listings and screenshots
- Handle app review process
OTA Updates
- Configure update channels (production, staging, etc.)
- Build and publish updates
- Manage rollout strategies
- Monitor update adoption
- Handle rollbacks if needed
Best Practices
- Use EAS Build for reliable production builds
- Test production builds before submission
- Implement proper error tracking and analytics
- Use release channels for staged rollouts
- Keep app store metadata up to date
- Monitor app performance in production
Resources
For more information, see the source repository.