expo-deployment

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

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

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, Play Store, and web involves complex credentials, build profiles, store metadata, and CI/CD setup. This Skill consolidates the entire EAS (Expo Application Services) deployment workflow into one place so you can build, submit, and automate releases without hunting through documentation. ## Core Features & Use Cases - Multi-Platform Builds & Submissions: Run production builds for iOS and Android, submit to App Store Connect and Google Play, and deploy web builds via EAS Hosting. - Store-Specific Guides: Detailed references for TestFlight beta testing, iOS App Store review, Google Play tracks and staged rollouts, and App Store metadata/ASO optimization. - CI/CD Automation: Ready-to-use EAS Workflows YAML for PR previews, tag-based releases, and automated build-and-submit pipelines. - Use Case: You just finished a feature in your Expo app. Run a production build, push it to TestFlight for internal testers, then promote it to the App Store with phased release—all using the commands and configs in this Skill. ## Quick Start Ask the AI to build and submit your Expo app to TestFlight using EAS with a production profile.

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 your iOS app 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 build number conflicts.

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

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

Does EAS support CI/CD automation for app releases?

Yes, EAS Workflows let you define YAML files in .eas/workflows to automate builds, submissions, OTA updates, and web deploys. You can trigger them on pushes, tags, pull requests, schedules, or manual dispatch, with job dependencies between build and submit steps.

Why does my App Store submission fail with version errors?

The error occurs when the build number is not higher than a previously uploaded build. Set appVersionSource to remote and autoIncrement to true in eas.json so EAS manages version codes and build numbers automatically.

Can I manage App Store metadata and keywords from the command line?

Yes, EAS Metadata uses a store.config.json file to manage titles, subtitles, keywords, descriptions, and release settings. Run eas metadata:pull to fetch existing metadata and eas metadata:push to upload changes, though it currently supports only the Apple App Store in preview.