Catalog
expo/expo-dev-client

expo

expo-dev-client

Framework (OSS). Build and distribute Expo development clients locally or via TestFlight for internal testing. For production TestFlight releases and store submission, use the eas-app-stores skill.

global
New~1.0k
v1.0Saved Jul 11, 2026

Use EAS Build to create development clients for testing native code changes on physical devices. Use this for creating custom Expo Go clients for testing branches of your app.

Free locally; cloud builds are paid. expo-dev-client itself is open source and building locally is free. Building or distributing via EAS Build/TestFlight uses your EAS plan's build minutes and needs a paid Apple Developer account for device/TestFlight distribution. See https://expo.dev/pricing.

Important: When Development Clients Are Needed

Development clients are the recommended setup for any real or production app. Expo Go is a playground for learning and quick experiments with the native libraries it bundles; most apps outgrow it and move to a development client. See Expo Go vs. development builds for the full reasoning.

You need a dev client ONLY when using:

  • Local Expo modules (custom native code)
  • Apple targets (widgets, app clips, extensions)
  • Third-party native modules not in Expo Go
  • Config plugins, or testing remote push notifications and App/Universal Links

EAS Configuration

Ensure eas.json has a development profile:

{
  "cli": {
    "version": ">= 16.0.1",
    "appVersionSource": "remote"
  },
  "build": {
    "production": {
      "autoIncrement": true
    },
    "development": {
      "autoIncrement": true,
      "developmentClient": true
    }
  },
  "submit": {
    "production": {},
    "development": {}
  }
}

Key settings:

  • developmentClient: true - Bundles expo-dev-client for development builds
  • autoIncrement: true - Automatically increments build numbers
  • appVersionSource: "remote" - Uses EAS as the source of truth for version numbers

Building for TestFlight

Build iOS dev client and submit to TestFlight in one command:

eas build -p ios --profile development --submit

This will:

  1. Build the development client in the cloud
  2. Automatically submit to App Store Connect
  3. Send you an email when the build is ready in TestFlight

After receiving the TestFlight email:

  1. Download the build from TestFlight on your device
  2. Launch the app to see the expo-dev-client UI
  3. Connect to your local Metro bundler or scan a QR code

Building Locally

Build a development client on your machine:

# iOS (requires Xcode)
eas build -p ios --profile development --local

# Android
eas build -p android --profile development --local

Local builds output:

  • iOS: .ipa file
  • Android: .apk or .aab file

Installing Local Builds

Install iOS build on simulator:

# Find the .app in the .tar.gz output
tar -xzf build-*.tar.gz
xcrun simctl install booted ./path/to/App.app

Install iOS build on device (requires signing):

# Use Xcode Devices window or ideviceinstaller
ideviceinstaller -i build.ipa

Install Android build:

adb install build.apk

Building for Specific Platform

# iOS only
eas build -p ios --profile development

# Android only
eas build -p android --profile development

# Both platforms
eas build --profile development

Checking Build Status

# List recent builds
eas build:list

# View build details
eas build:view

Using the Dev Client

Once installed, the dev client provides:

  • Development server connection - Enter your Metro bundler URL or scan QR
  • Build information - View native build details
  • Launcher UI - Switch between development servers

Connect to local development:

# Start Metro bundler
npx expo start --dev-client

# Scan QR code with dev client or enter URL manually

Troubleshooting

Build fails with signing errors:

eas credentials

Clear build cache:

eas build -p ios --profile development --clear-cache

Check EAS CLI version:

eas --version
eas update
Files2
2 files · 1.4 KB

Select a file to preview

Overall Score

84/100

Grade

B

Good

Safety

85

Quality

86

Clarity

85

Completeness

80

Summary

This skill teaches developers when and how to build Expo development clients—custom native app environments for testing branches and native code changes on physical devices. It covers EAS configuration, cloud and local builds for iOS/Android, installation on devices/simulators, and connection to Metro bundler. No file writes or destructive operations are performed.

Detected Capabilities

shell command execution (eas build, adb, xcrun)file extraction (tar -xzf)file installation (simctl, ideviceinstaller, adb install)local build operationscredentials management (eas credentials)external API interaction (EAS Cloud build service)

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

development client setuptesting native codeexpo build eascustom dev clienttestflight distributionbuild local development client

Risk Signals

INFO

External network requests to EAS Cloud (eas build command)

Building for TestFlight / Building Locally sections
INFO

Credentials access via 'eas credentials' for signing

Troubleshooting section
INFO

File extraction from tar.gz archives

Installing Local Builds section

Referenced Domains

External domains referenced in skill content, detected by static analysis.

docs.expo.devexpo.dev

Use Cases

  • Test native code changes on physical iOS and Android devices using development clients
  • Migrate from Expo Go to a custom development client for production-ready apps
  • Configure and build development clients locally or via EAS Cloud (TestFlight)
  • Install compiled development clients (.ipa, .apk) on simulators and devices
  • Connect development clients to local Metro bundler for live code reloading

Quality Notes

  • Well-structured with clear section hierarchy and practical command examples
  • Explains when development clients are needed, distinguishing from Expo Go use cases
  • Includes both local and cloud build workflows with concrete steps
  • References external documentation (docs.expo.dev) for deeper context
  • Covers multiple platforms (iOS, Android) and deployment targets (simulator, device, TestFlight)
  • Pricing and free-tier limitations are explicitly documented upfront
  • Configuration example is complete with explanation of key settings
  • Troubleshooting section addresses common failure modes
  • Commands are production-ready and follow Expo CLI conventions
Model: claude-haiku-4-5-20251001Analyzed: Jul 11, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Add expo/expo-dev-client to your library

Command Palette

Search for a command to run...