home / skills / expo / skills / expo-dev-client

expo-dev-client skill

/plugins/expo-app-design/skills/expo-dev-client

This skill helps you build and manage Expo development clients with EAS for local or TestFlight deployments.

npx playbooks add skill expo/skills --skill expo-dev-client

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.4 KB
---
name: expo-dev-client
description: Build and distribute Expo development clients locally or via TestFlight
version: 1.0.0
license: MIT
---

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.

## Important: When Development Clients Are Needed

**Only create development clients when your app requires custom native code.** Most apps work fine in Expo Go.

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

**Try Expo Go first** with `npx expo start`. If everything works, you don't need a dev client.

## EAS Configuration

Ensure `eas.json` has a development profile:

```json
{
  "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:

```bash
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:

```bash
# 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:

```bash
# 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):

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

Install Android build:

```bash
adb install build.apk
```

## Building for Specific Platform

```bash
# 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

```bash
# 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:

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

# Scan QR code with dev client or enter URL manually
```

## Troubleshooting

**Build fails with signing errors:**
```bash
eas credentials
```

**Clear build cache:**
```bash
eas build -p ios --profile development --clear-cache
```

**Check EAS CLI version:**
```bash
eas --version
eas update
```

Overview

This skill helps you build and distribute Expo development clients locally or via TestFlight so you can test native code changes on physical devices. It guides configuration of EAS build profiles, running cloud or local builds, and installing dev-client binaries on iOS and Android. Use it to create custom Expo Go-style clients when your app requires native modules or Apple-specific targets.

How this skill works

The skill inspects your Expo project configuration and shows the required eas.json development profile settings including developmentClient and appVersionSource. It runs EAS build commands (cloud or local), automates submission to TestFlight if requested, and provides the installation steps for simulator, device, and Android installs. It also surfaces common commands to check build status, clear caches, and fix signing issues.

When to use it

  • You need custom native code, local Expo modules, or third-party native libraries not available in Expo Go
  • Testing Apple-specific targets like widgets, app clips, or extensions
  • Distributing a development client to testers via TestFlight
  • When you want to run a development client on a simulator or a physical device for debugging native behavior

Best practices

  • Try Expo Go first with npx expo start; only build a dev client when necessary
  • Add a development profile in eas.json with developmentClient:true and autoIncrement:true
  • Use appVersionSource: "remote" so EAS controls version numbers consistently
  • Prefer cloud builds with --submit for TestFlight distribution and use --local for faster iterative testing
  • Keep your EAS CLI up to date and validate credentials with eas credentials before iOS builds

Example use cases

  • Create a custom dev client to test a new native module on Android and iOS
  • Build and submit an iOS dev client to TestFlight for teammate testing using eas build --profile development --submit
  • Perform a local iOS build, extract the .app and install it on the simulator with xcrun simctl
  • Install an Android build locally with adb install build.apk for quick device verification

FAQ

Do I always need a development client?

No. Use Expo Go first. Create a dev client only when your app uses custom native code, Apple targets, or native libraries not included in Expo Go.

How do I submit a dev client to TestFlight?

Run eas build -p ios --profile development --submit. EAS builds the client, submits to App Store Connect, and emails you when it’s available in TestFlight.

What files do local builds produce?

Local iOS builds output an .ipa (or .app inside .tar.gz for simulator). Android outputs an .apk or .aab.

Build signing fails—what now?

Run eas credentials to inspect and fix signing. For cache problems use eas build -p ios --profile development --clear-cache.