expo-deployment

Automate Expo app builds, submissions, and deployments via EAS CLI.

52|22|Updated Nov 9, 2022
One-click install
npx skills add https://github.com/satsigner/satsigner --skill expo-deployment-satsigner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-deployment
Source: https://github.com/satsigner/satsigner/tree/main/.cursor/skills/expo-deployment
Command: npx skills add https://github.com/satsigner/satsigner --skill expo-deployment-satsigner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This guide removes friction from building, submitting, and deploying Expo applications across iOS, Android, and web by consolidating EAS commands, store submission steps, metadata management, and CI/CD workflows into a single actionable reference.

Core Features & Use Cases

  • Cross-platform builds and submissions: Build and submit iOS and Android production releases and TestFlight builds using EAS CLI.
  • Web hosting and PR previews: Deploy web builds and generate preview URLs for pull requests with EAS Hosting and workflow examples.
  • Store metadata and automation: Manage App Store metadata via EAS Metadata, configure Play Store service accounts, and automate releases with EAS Workflows.
  • CI/CD integration: Ready-to-use workflow examples for automated releases, PR previews, and staged rollouts across platforms.
  • Use Case: A mobile team preparing a v1.0 release can run production builds, push metadata, submit to TestFlight and Play Console, and trigger a staged rollout from a single CI pipeline.

Quick Start

Log in to EAS CLI and initialize your project so eas.json is created, then run a production build and submit to the stores.

Frequently Asked Questions about expo-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Expo EAS deployment to the App Store and Play Store?

Expo EAS deployment automates cross-platform submissions by running EAS CLI commands for iOS App Store and Google Play Store production releases. It consolidates build, submit, and metadata management steps into a single CI/CD pipeline using configured eas.json.

Can I generate PR preview URLs for Expo web builds using EAS?

Yes, EAS Hosting supports deploying web builds and generating preview URLs for pull requests. Ready-to-use workflow examples automate PR previews and staged rollouts across platforms.

What credentials do I need to configure for EAS builds and submissions?

EAS builds require an initialized project with eas.json, EAS CLI login, and optionally store.config.json. iOS submissions need App Store Connect credentials, while Android requires a Play Store service account.

How does EAS Metadata management work for TestFlight distribution?

EAS Metadata management handles App Store metadata updates and TestFlight distribution. It pushes metadata and submits builds to TestFlight through EAS CLI commands integrated within automated release workflows.

What's the best way to set up CI/CD workflows for staged Expo app rollouts?

The best way to configure CI/CD workflows for staged rollouts is using EAS Workflows. It provides ready-to-use examples to automate releases, PR previews, and staged production rollouts across iOS and Android.