---
title: Expo Eas Production Pipeline
category: product
entity_type: skill
price: $15
canonical: https://forgehouse.ai/skills/expo-eas-production-pipeline/
lang: en
hreflang_alt: https://forgehouse.ai/tr/skiller/expo-eas-production-pipeline/
last_updated: 2026-06-20
---

# Expo Eas Production Pipeline

> React Native + Expo EAS production deploy pipeline Build (development/preview/production)…

An end-to-end React Native + Expo EAS publishing discipline that takes a mobile app from build to live store release and beyond. It covers EAS Build/Submit/Update, iOS provisioning and Android keystore signing, staged OTA rollouts, crash-free monitoring, and full privacy compliance, so shipping an app means more than just uploading a binary.

## Use cases
- Setting up eas.json with development, preview and production build profiles
- Configuring env-specific bundle IDs and runtime permissions in app.config.ts
- Running a staged OTA rollout (10% then 50% then 100%) with crash-free rate checks
- Deciding between an OTA update and a new native build for a given change
- Filling the Apple Privacy Manifest and Google Play Data Safety form correctly
- Wiring a tag-based GitHub Actions pipeline with auto-submit and Sentry source maps

## Benefits
- Catch crashes before they reach all users through TestFlight soak and percentage rollouts
- Avoid App Store and Play rejections by pre-clearing common guideline and privacy issues
- Roll back a bad release in minutes instead of waiting for another store review
- Stay compliant on mobile permissions and data disclosure across iOS and Android

## What’s included
- Complete eas.json with build profiles plus iOS and Android submit configuration
- app.config.ts pattern for variant bundle IDs, ATT prompt copy and runtime permissions
- GitHub Actions workflow for production build, auto-submit and source map upload
- Bash script for safe staged OTA rollout with crash-free thresholds and rollback
- Apple Privacy Manifest example plus a consent service for runtime permission handling
- Pre-submission checklist, store-review guideline notes and 12 documented anti-patterns

## Who it’s for
Mobile and DevOps engineers shipping production React Native apps who need a repeatable, compliant pipeline rather than fragile one-off store uploads.

## How it runs
The skill takes a React Native app from repo to both stores through a gated pipeline where nothing skips a checkpoint. The run it executes:
1. Pre-flight gate: expo-doctor at zero errors, npm audit at zero high or critical, bundle size under 50MB iOS and 40MB Android, expo install --check confirming no native dependency drift, and provisioning credentials with more than 30 days left.
2. Configures eas.json with three profiles (development as simulator APK, preview as internal distribution, production with autoIncrement buildNumber and remote managed credentials) plus app.config.ts that switches bundle ID and app name per variant so dev, preview and prod install side by side.
3. Compliance pass before any submit: KVKK consent modal with runtime permissions, the Apple Privacy Manifest (PrivacyInfo.xcprivacy) with tracking domains listed, ATT prompt timed after onboarding instead of at launch, and the Google Play Data Safety form matched to every SDK actually shipped.
4. Builds preview first and soaks it: TestFlight plus internal track on 5+ devices for around 7 days with zero crashes before a production build is even considered.
5. Production deploy is tag-triggered in CI: eas build with auto-submit pushes to App Store Connect and Play Console, Sentry source maps upload automatically so crashes correlate to the exact build SHA.
6. JS-only patches go out as OTA updates on a staged rollout: 10% of users, 24-hour soak watching the crash-free rate against a 99.5% threshold, then 50%, then 100%. A spike triggers rollback to the previous bundle with one command. Native changes never ship OTA, they get a new build.

## FAQ
### Does this work with a bare React Native app or only Expo-managed projects?
It is built around EAS, so it assumes the Expo toolchain for build, submit and update. Bare React Native can adopt EAS, but the provisioning and OTA discipline here is written for the Expo workflow.

### Can a staged OTA rollout actually pull back a bad release without a full store review?
For JavaScript and asset changes, yes, the staged update lets you halt or roll back while watching crash-free rate, no store cycle needed. Anything that touches native modules still requires a new store build, and the pipeline says so.

### Does it get my app through App Store review or handle the listing?
No, it covers the build-to-release pipeline, signing, staged rollout and crash monitoring, not your store listing or review appeals. Content guidelines and marketing copy sit outside its scope.

## Price
$15, one-time, no subscription. VAT included.

Related guide: [AI code review and developer workflow](https://forgehouse.ai/guides/ai-code-review/)