Skip to content
cccskills
FreePublished on GitHub

expo-dev-client

Build development clients for Expo apps that use custom native code. Covers local and cloud builds, device installation, TestFlight distribution, and connecting installed clients to a local development server.

OriginalShow the original description

Build and distribute Expo development clients locally or via TestFlight

See how to install

Good for

  • Test custom native modules on physical devices
  • Distribute an iOS development build through TestFlight
  • Build iOS or Android development clients locally
  • Connect an installed client to a development server

Files included (1)

  • SKILL.md3.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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:

{
  "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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

agent-device

FreeSummary

Guide app automation on iOS, tvOS, macOS, and Android using help matched to the installed agent-device CLI. Tasks include screen inspection, taps, text entry, scrolling, and collecting logs, network information, or performance evidence.

  • Navigate apps and verify the resulting screens
  • Automate text entry and scrolling
  • Capture screenshots and inspect interface information
CherryHQ/cherry-studio-app4KUpdated Oct 20, 2026

Build app screens with Expo Router using guidance on layout, navigation, native tabs, and animations. It covers route organization and styling patterns, with Expo Go as the starting point for testing.

  • Build screens and navigation with Expo Router
  • Organize native tabs and navigation stacks
  • Add link previews and context menus
CherryHQ/cherry-studio-app4KUpdated Oct 20, 2026

diagnose

FreeSummary

Diagnose bugs, intermittent failures, and performance regressions through structured logging and reproduction. It ranks possible causes with confidence scores, tests competing explanations, and reports whether the evidence proves the cause or leaves the diagnosis incomplete.

  • Trace the cause of a reproducible bug
  • Investigate intermittent failures through repeated runs
  • Compare possible causes of browser or device failures
CherryHQ/cherry-studio-app4KUpdated Oct 20, 2026

Drive repeated debugging cycles with the required diagnose skill: establish evidence for a cause, choose one focused fix, and rerun the original validation. Reassess after each change until no credible fix remains or further progress requires user input.

  • Repeating bug fixes and verification until validation is clean
  • Checking performance changes against original measurements
  • Investigating regressions after each fix
CherryHQ/cherry-studio-app4KUpdated Oct 20, 2026

Check published EAS Updates from the command line using crash rates, user counts, and payload size. Compare adoption of the app's bundled version and over-the-air updates, with JSON output for automated health checks.

  • Check update health after publishing
  • Compare crash rates with a previous release
  • Compare bundled and over-the-air update adoption
CherryHQ/cherry-studio-app4KUpdated Oct 20, 2026

Create and edit EAS workflow YAML files to automate builds and deployment for Expo projects. The skill consults current documentation and validates configuration structure, required parameters, job dependencies, and expressions against the published schema.

  • Create an EAS workflow for builds and deployment
  • Edit workflow triggers and job dependencies
  • Validate existing workflow YAML files
CherryHQ/cherry-studio-app4KUpdated Oct 20, 2026

See all skills by CherryHQ

Report a problem with this skill