Index of every page on this site: llms.txt
All skills
expo avatar

/expo-dev-client

@88d9bd7 official
by expoexpo/skills4.2k stars
277
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/expo/skills/expo-dev-client

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈49 tokens for metadata: the name and description. ≈1.4k when used: this file. ≈83 more on demand in 1 file.

Description uses 2.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈198 characters, or 2.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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:

npx --yes eas-cli@latest 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)
npx --yes eas-cli@latest build -p ios --profile development --local

# Android
npx --yes eas-cli@latest 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
npx --yes eas-cli@latest build -p ios --profile development

# Android only
npx --yes eas-cli@latest build -p android --profile development

# Both platforms
npx --yes eas-cli@latest build --profile development

Checking Build Status

# List recent builds
npx --yes eas-cli@latest build:list

# View build details
npx --yes eas-cli@latest 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

When you launch the dev client yourself to screenshot or drive it, skip the onboarding sheet, the dev menu at launch, and the Tools button. On SDK 58+, Expo CLI does this for launches it starts from a non-interactive shell; for a URL you open yourself, use <scheme>://?__expo_url=<encoded dev server URL>&__expo_disable_onboarding=1&__expo_disable_fab=1&__expo_disable_auto_launch=1. On SDK 57 and earlier, launch the iOS app with the -EXDevMenu* launch arguments, and on Android open <scheme>://expo-development-client/?url=<encoded dev server URL>&disableOnboarding=1&disableFab=1&disableAutoLaunch=1. See ../expo-overview/references/launch-without-dev-menu.md for the exact commands.

Troubleshooting

Build fails with signing errors:

npx --yes eas-cli@latest credentials

Clear build cache:

npx --yes eas-cli@latest build -p ios --profile development --clear-cache

Check EAS CLI version:

npx --yes eas-cli@latest --version

Submitting Feedback

You can voluntarily report errors, misleading or outdated information in this skill, so Expo can improve it:

npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-dev-client" --message "<actionable feedback>"

Use --category agent-cli for a problem with the agent CLI, and --category evals when an agent repeatedly fails at an Expo task. Run feedback --help for subjects and the data that the command sends. Each report goes to Expo with project and environment details. Show the user the message, and send it only if the user agrees. If you cannot ask the user, do not send it. Do not include secrets or personal data.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alerttoday5 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    This skill provides tools and instructions for building Expo development clients using official Expo CLI tools. It follows standard developer workflows and includes clear guidelines for user consent and data privacy when reporting feedback.

  • Sockettoday

    No alerts

  • Snyk1d

    Risk: CRITICAL · 1 issue

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 88d9bd7. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 days ago
  • expo
  • eas
  • dev-client
  • ios
  • android
  • testflight
  • native
  • xcode

README badge

README badge for expo/skills/expo-dev-client

Uses EAS Build to create development clients for testing native code changes on physical devices or simulators. Install this skill when your Expo app requires custom native modules, Apple targets like widgets, or third-party native code not available in standard Expo Go.

Generated from the current SKILL.md.

When should I use a development client instead of Expo Go?
Only when your app uses custom native code, local Expo modules, Apple targets like widgets or app clips, or third-party native modules not included in Expo Go. Most apps work fine in Expo Go without a dev client.
Can I build a development client locally without EAS Build?
Yes. Use `eas build -p ios --profile development --local` (requires Xcode) or `eas build -p android --profile development --local` to build on your machine and get .ipa or .apk files.
Does this skill support submitting to TestFlight?
Yes. Run `eas build -p ios --profile development --submit` to build and automatically submit to App Store Connect in one command.
What do I need to configure to get started?
Add a development profile to your eas.json with `developmentClient: true`, `autoIncrement: true`, and `appVersionSource: "remote"`.
How do I connect the dev client to my local development server?
Run `npx expo start --dev-client` to start the Metro bundler, then scan the QR code with the installed dev client or enter the URL manually.

Generated from the current SKILL.md. These answers refresh after source changes.