expo-deployment

Automate Expo app builds and submissions to iOS, Android, and web.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/mjamore/ticked-off --skill expo-deployment-mjamore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-deployment
Source: https://github.com/mjamore/ticked-off/tree/main/.agents/skills/expo-deployment
Command: npx skills add https://github.com/mjamore/ticked-off --skill expo-deployment-mjamore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Deploying Expo apps to multiple platforms requires coordinating EAS builds, store credentials, metadata, and CI workflows, which is error-prone and time consuming. This Skill consolidates best practices and commands so teams can produce reproducible builds, submit binaries, and deploy web previews without manual steps.

Core Features & Use Cases

  • Cross-platform releases: Build and submit production iOS and Android binaries and deploy web builds using EAS.
  • Store submissions and metadata: Manage App Store and Play Store submissions, metadata (EAS Metadata / store.config), and TestFlight distribution.
  • CI/CD automation: Provide example EAS Workflows for automated releases, PR previews, and staged rollouts with service account and secret handling.
  • Credential and config guidance: Instructions for App Store Connect API keys, Google Play service accounts, eas.json profiles, and safe storage patterns.
  • Use case: Automate nightly builds that produce TestFlight previews, push metadata, and deploy a web PR preview to validate pull requests.

Quick Start

Build and submit a production iOS and Android release using EAS with a configured eas.json and the required App Store Connect or Google Play credentials.

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 app releases to the App Store and Google Play?

Automate Expo app releases by configuring EAS build and submit commands within CI/CD workflows. This Skill provides EAS Workflows to produce reproducible iOS and Android binaries, submit them to stores, and deploy web builds without manual steps.

What credentials do I need to submit an Expo app to TestFlight?

To submit an Expo app to TestFlight, you need an App Store Connect API key and configured eas.json profiles. This Skill guides safe storage patterns and credential setup for automated iOS distribution.

Can I deploy Expo web previews for pull requests using EAS?

Yes, you can deploy Expo web previews for pull requests using EAS Workflows. This Skill provides CI/CD automation examples to build and host PR previews, validating changes before merging.

How do I manage App Store and Play Store metadata for EAS submissions?

Manage App Store and Play Store metadata during EAS submissions using EAS Metadata or store.config.json. This Skill consolidates commands to push metadata updates alongside production binary submissions.

Does this Skill require a specific eas.json configuration to build Expo apps?

Yes, this Skill requires a configured eas.json file with defined build profiles. It uses these profiles alongside EAS CLI to execute cross-platform releases, store submissions, and CI/CD automation.

What is the best way to set up Google Play service accounts for Expo deployments?

The best way to set up Google Play service accounts for Expo deployments is by configuring API keys within your CI environment. This Skill provides instructions for safe credential handling and service account integration for Android submissions.