expo-dev-client

Build and distribute Expo development clients for testing native code changes.

34|2|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/FilenCloudDienste/filen-ts --skill expo-dev-client-filenclouddienste
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-dev-client
Source: https://github.com/FilenCloudDienste/filen-ts/tree/main/.claude/skills/expo-dev-client
Command: npx skills add https://github.com/FilenCloudDienste/filen-ts --skill expo-dev-client-filenclouddienste

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of slow or unreliable testing of custom native code changes in Expo apps by letting you run a development client on physical devices and simulators.

Core Features & Use Cases

  • EAS development-client builds: Create dev clients configured to include expo-dev-client so your app can load native changes that go beyond what Expo Go supports.
  • TestFlight and local build workflows: Build for iOS via EAS and submit to TestFlight, or generate local installable artifacts for both iOS and Android.
  • Metro bundler integration: Connect the installed dev client to your local Metro bundler using a URL or QR code for fast iteration during development.

Use Case: You’re working on an app branch that uses Apple targets (widgets/app clips/extensions) or a local/native module, and you need real-device testing to verify native behavior before production release.

Quick Start

Ask: "Build an Expo development client for my iOS app using the development profile and submit it to TestFlight with EAS."

Frequently Asked Questions about expo-dev-client

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test custom native code changes in a React Native Expo app?

Use an Expo development client to test custom native code changes on physical devices or simulators. You build a dev client configured with expo-dev-client, which supports native modules not available in Expo Go.

When do I need an Expo development client instead of Expo Go?

You need an Expo development client when your project uses Apple targets like widgets or extensions, local native modules, or third-party native modules. Expo Go cannot load these custom native code changes during development.

How do I build and submit an Expo dev client to TestFlight using EAS?

To build and submit an Expo dev client to TestFlight, use EAS Build with a development profile that has developmentClient enabled. This creates a remote build and submits it directly to TestFlight.

Can I build Expo development clients locally for both iOS and Android?

Yes, you can generate local installable artifacts for both iOS and Android development clients. This allows you to install the dev client directly on physical devices without using remote EAS Build submissions.

How do I connect an installed Expo dev client to my local Metro bundler?

Connect the installed Expo dev client to your local Metro bundler using a URL or QR code. This integration enables fast iteration and hot reloading during development.

Do I need an EAS development profile to create an Expo dev client build?

Yes, creating an Expo dev client build requires an EAS development profile with the developmentClient setting enabled. This profile configures the build to include the necessary dev client dependencies.