expo-dev-client

por expo

Crea clientes de desarrollo Expo personalizados para probar código nativo en dispositivos físicos mediante EAS Build o de forma local. Solo es necesario al usar módulos nativos personalizados, destinos de Apple (widgets, app clips) o código nativo de terceros que no esté en Expo Go; prueba primero Expo Go con npx expo start. Admite compilaciones en la nube con envío automático a TestFlight o compilaciones locales en tu máquina, generando archivos .ipa (iOS) o .apk/.aab (Android). Requiere configuración de eas.json con un perfil de desarrollo que establezca...

npx skills add https://github.com/expo/skills --skill expo-dev-client

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.

Más skills de expo

add-app-clip
expo
Agregar un destino de App Clip de iOS a una app de Expo. Úsalo cuando el usuario mencione App Clip, AASA, apple-app-site-association, appclips, smart app banner, o quiera enviar…
android-e2e-testing
expo
Prueba las funciones de Expo Router en emuladores de Android usando ADB. Úsalo después de implementar funciones nativas de Android o al verificar el comportamiento de la interfaz de usuario en Android.
android-jetpack-compose
expo
Úsalo al crear interfaces de Android con Jetpack Compose, gestionar estado con remember/mutableStateOf o implementar patrones de UI declarativos.
api-routes
expo
Directrices para crear rutas de API en Expo Router con EAS Hosting
building-native-ui
expo
Guía completa para crear aplicaciones nativas con Expo, que abarca enrutamiento, estilos, componentes y convenciones de plataforma. Cubre los fundamentos de Expo Router, pestañas nativas, navegación en pila, modales y hojas de formulario con convenciones detalladas de estructura de rutas. Incluye reglas de estilo alineadas con las Guías de Interfaz Humana de Apple: diseños flexbox, manejo de áreas seguras, animaciones, sombras mediante CSS boxShadow y patrones de diseño responsivo. Documenta preferencias de librerías (expo-image para SF Symbols, expo-audio, expo-video,...).
building-ui
expo
Guía completa para crear aplicaciones hermosas con Expo Router. Cubre fundamentos, estilos, componentes, navegación, animaciones, patrones y pestañas nativas.
cicd-workflows
expo
Ayuda a comprender y escribir archivos YAML de flujos de trabajo EAS para proyectos de Expo. Usa esta habilidad cuando el usuario pregunte sobre CI/CD o flujos de trabajo en un contexto de Expo o EAS,…
data-fetching
expo
Úsalo al implementar o depurar CUALQUIER solicitud de red, llamada a API o recuperación de datos. Cubre fetch API, axios, React Query, SWR, manejo de errores, almacenamiento en caché…