expo-deployment

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

Updated May 28, 2026
One-click install
npx skills add https://github.com/qbstabletampa-creator/firmware-foundation-studios --skill expo-deployment-qbstabletampa-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: expo-deployment
Source: https://github.com/qbstabletampa-creator/firmware-foundation-studios/tree/main/archive/apps/manna-catch/.agents/skills/expo-deployment
Command: npx skills add https://github.com/qbstabletampa-creator/firmware-foundation-studios --skill expo-deployment-qbstabletampa-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Shipping an Expo app to production involves juggling Apple credentials, Google service accounts, build profiles, store metadata, and CI/CD pipelines. This Skill consolidates the entire EAS (Expo Application Services) deployment workflow into one place so you can build, submit, and release across iOS, Android, and web without memorizing platform-specific procedures. ## Core Features & Use Cases - Multi-Platform Builds & Submissions: Run production builds and submit to App Store Connect and Google Play with single EAS CLI commands, including the npx testflight shortcut for iOS beta testing. - Store Metadata & ASO Management: Manage App Store listings, keywords, localization, age ratings, and release strategies as code via store.config.json and eas metadata:push. - CI/CD Automation with EAS Workflows: Automate releases on git tags, generate PR previews for web and native (via EAS Update), and configure staged rollouts on Play Store tracks. - Use Case: You are ready to ship version 2.0 of your React Native app. Use this Skill to configure eas.json with auto-incrementing versions, build both platforms, submit iOS to TestFlight for external testers, push optimized App Store metadata, and set up a tag-triggered release workflow. ## Quick Start Ask the AI to build your Expo app for iOS production and submit it to TestFlight using EAS.

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 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, and enable autoIncrement in eas.json to avoid bundle version errors.

How to deploy an Expo app to Google Play Store with EAS?▼

Create a Google Cloud service account with release permissions, link it in Play Console API access, and reference the JSON key in eas.json under submit.production.android. Then run `eas build -p android --profile production --submit` to build and upload an AAB.

Does EAS Metadata support Google Play Store listings?▼

No. EAS Metadata is currently in preview and supports the Apple App Store only. It manages titles, keywords, descriptions, age ratings, and release settings through a store.config.json file pushed with `eas metadata:push`.

Why does my iOS submission fail with 'bundle version must be higher'?▼

Each App Store upload requires an incremented build number (CFBundleVersion). Set `autoIncrement: true` in your eas.json production build profile and use `appVersionSource: "remote"` so EAS manages build numbers automatically.

Can I automate Expo releases with CI/CD?▼

Yes. EAS Workflows let you define YAML files in .eas/workflows that trigger builds, submissions, OTA updates, and web deploys on push, tags, or pull requests. Jobs support dependencies via `needs` and conditional execution.

What are the limitations of TestFlight beta testing?▼

TestFlight allows up to 100 internal testers with immediate access and up to 10,000 external testers who require a one-time Beta App Review. Builds expire after 90 days, so apps must be re-submitted or released to the App Store before expiration.