Text of expo.dev › services › workflows as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout.

Open the live page

Expo Workflows: mobile CI/CD built for React Native

Expo Workflows Mobile CI/CD built for React Native Expo Workflows is a mobile CI/CD service for React Native and Expo apps that builds, signs, submits, and ships over-the-air updates in one pipeline. Add it to your existing CI, or run everything here. Explore Expo Workflows $ eas workflow:run 86% of State of React Native 2025 respondents used Expo CLI 50k+ GitHub stars 99.9% uptime SLA on Enterprise 10M+ Weekly npm downloads Integrate then scale You don't need to rip out your CI.

Most teams start by moving mobile builds to Expo Workflows, then expand over time. Your current GitHub Actions setup GitHub Actions runs everything, from lint and tests to builds, signing and store submissions. You manage macOS runners, a Fastlane Match repo, keystore secrets and well over a hundred lines of YAML. ✕ macOS runners billed per minute ($0.062 standard, $0.102 for M2 Pro) ✕ A stack of signing secrets to rotate ✕ A Fastlane Match repo to maintain ✕ A full native rebuild on every push Step 1: Add Expo Workflows alongside GitHub Actions Keep GitHub Actions for lint, tests and web builds.

Move mobile builds, store submissions and OTA updates to Expo Workflows with a single CLI call. ✓ No macOS runners in GitHub Actions ✓ One secret (EXPO_TOKEN) instead of signing config in GitHub ✓ iOS builds run on M4 Pro workers, billed per build ✓ Lint and tests stay where they are Learn more Step 2: Full pipeline in Expo Workflows Move everything to Expo Workflows. Trigger runs straight from GitHub events, and fingerprinting detects whether native code changed so only the jobs that matter run. ✓ No GitHub Actions required ✓ JavaScript-only changes skip the full native build ✓ A build-and-submit pipeline in about 20 lines of YAML ✓ Managed hardware, signing and caching Learn more Purpose-built infrastructure Pre-packaged mobile jobs Build, submit, TestFlight, update, fingerprint, repack, Maestro (alpha) and Slack jobs you combine in YAML.

A build job is about six lines, with no bash scripts or Fastlane lanes. M4 Pro Apple Silicon iOS builds and other macOS jobs run on M4 Pro workers, with a fresh macOS VM for every build. Average build jobs ran about 1.85x faster after the move to M4 Pro. Managed signing Expo stores your keystore, certificates and profiles, so one EXPO_TOKEN replaces base64 keystore secrets, Fastlane Match and Apple API keys in your CI.

Credentials are encrypted at rest and injected at build time. Lightweight jobs Slack notifications, build lookups and approval gates are pre-packaged jobs, so you don't script them. Automatic caching Dependency caching, compiler caching and hardware upgrades are applied for you, with no config changes. Run from anywhere Trigger from GitHub events or a schedule, call eas workflow:run from any CI, or start a run from your terminal.

DevOps Tax The real cost of CI The invoice is only part of it. Maintaining runners, signing and store scripts takes engineering time every week, and slow pipelines delay every release. Expo Workflows takes that work off your team so engineers can spend it on features. Efficient Expo Workflows and GitHub Actions Expo Workflows works as the mobile half of a GitHub Actions setup. GitHub Actions keeps running lint and tests, and Expo handles iOS and Android builds, code signing and store submission.

Learn more Deployment speeds Expo Workflows picks the fastest path based on what changed in your code. Full build Native code changed? Expo Workflows runs a full compile, sign and submit on M4 Pro workers. Learn more Repack No native changes? Expo Workflows reuses a matching build, bundles your new JavaScript and re-signs it, so there's no full compile. In one large app, that took a build from about 23 minutes to about 5.

Learn more OTA update JavaScript-only hotfix? Publish an over-the-air update to users' devices in seconds, with no rebuild. Learn more Battle tested CI/CD From indie developers to enterprise, teams like Hipcamp, PrizePicks, and Infinite Red ship with Expo Workflows. “ Expo Workflows replaced our sluggish and brittle build process with something quick and dependable. Expo allows our engineers to focus on building features and not debugging build logs. ” Armaiz Adenwala Senior Software Engineer “ Setting up React Native CI/CD used to be difficult until I started using workflows.

Expo was already the best way to write React Native apps. Now it’s the best way to test and deploy them as well. ” Tyler Williams Software Engineer “ Workflows allowed us to replace large complex yaml files with pre-built jobs fully leveraging the power of EAS. It's made our pipelines feel effortless. ” Adam Tyler Software Engineer Frequently asked questions about Expo Workflows Frequently Asked Questions Expo Workflows is a CI/CD service from Expo for React Native and Expo apps.

It runs pre-packaged jobs for iOS and Android builds, App Store and Google Play submission, over-the-air updates and Maestro end-to-end tests, defined in YAML files in your repository. Expo Workflows is built specifically for React Native and Expo, with pre-packaged jobs for Expo Build, Expo Submit, Expo Update and fingerprint-based repacks. Bitrise supports more frameworks, including fully native iOS and Android apps, and offers a large step library and a visual workflow editor.

If your apps are React Native, Expo Workflows needs less configuration; if you also ship native-only apps, Bitrise covers both. Codemagic started with Flutter and supports React Native, native iOS and native Android, with pay-as-you-go per-minute pricing or fixed annual plans. Expo Workflows focuses on React Native and Expo, prices builds per build, and includes Expo Update for over-the-air updates plus pre-packaged fingerprint and repack jobs.

No. Many teams keep lint, type checks and unit tests in GitHub Actions and move only mobile builds, signing and store submission to Expo Workflows. A GitHub Actions job can start an Expo build or workflow with one EXPO_TOKEN secret, or you can trigger Expo Workflows directly from GitHub events. iOS builds and other macOS jobs run on M4 Pro workers, with a fresh macOS VM for every build. The medium macOS worker has 5 cores and 20 GB of RAM, and the large worker has 10 cores and 40 GB of RAM.

Large workers are available on paid plans. The Free plan includes 15 Android and 15 iOS builds and 60 minutes of CI/CD jobs a month. Starter is $19 a month with $45 of build credit, and Production is $199 a month with $225 of build credit and 2 concurrencies. After credit, builds cost $1 to $4 each depending on platform and worker size, and other jobs are billed per minute. Yes. Expo Build and Expo Submit replace App Center's build and distribution steps, and Expo Update replaces CodePush for over-the-air updates.

The Expo docs include a step-by-step guide to migrate from CodePush to Expo Update. Yes. Any job without a type is a custom job that runs your own shell commands, and jobs can be chained with needs, after and if conditions. Pre-packaged jobs such as build, submit and update accept hooks that run steps before or after the main action, and Expo Build supports custom build configs in YAML. Yes. Development builds can include any native library, config plugins change native settings during prebuild, and the Expo Modules API lets you write Swift and Kotlin modules.

If your project has no native folders, Expo Build runs prebuild for you; if it does, Expo Build uses your native folders as they are. One platform for everything from commit to release Get started with Expo Workflows