expo-dev-client

Automate Expo development client builds and distribution with EAS profiles.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tDalile/dotfiles --skill expo-dev-client-tdalile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-dev-client
Source: https://github.com/tDalile/dotfiles/tree/main/agents/skills/expo-dev-client
Command: npx skills add https://github.com/tDalile/dotfiles --skill expo-dev-client-tdalile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build and distribute Expo development clients to test custom native code changes on physical devices and simulators.

Core Features & Use Cases

  • Dev client creation for local native code testing across iOS and Android.
  • EAS integration for development profiles, automatic versioning, and streamlined submission.
  • Local and CI workflows for testing branches and sharing builds with teammates.

Quick Start

Start a development client for your app using the recommended EAS workflow to test custom native code.

Frequently Asked Questions about expo-dev-client

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

FAQPage Schema
How do I build an Expo dev client for testing custom native code on physical devices?

To build an Expo dev client, configure an EAS development profile with developmentClient set to true, then run the build process on macOS for iOS or your local environment for Android. This compiles your custom native code into a testable application for physical devices.

When do I need a custom Expo dev client instead of using Expo Go?

You need an Expo dev client when your project includes local native modules or custom native code that cannot be loaded through Expo Go. It allows you to test native code changes directly on physical devices and simulators across iOS and Android.

How do I distribute an Expo development client to TestFlight using EAS?

You can distribute an Expo development client to TestFlight by configuring your EAS profile for app store submission, enabling remote versioning, and submitting the build directly through the EAS CLI workflow. This automates the delivery of the development client to testers.

Can I automate version increments for Expo development builds with EAS?

Yes, EAS supports automatic build number increments and remote versioning for Expo development builds. This ensures each build submitted to TestFlight or distributed to teammates has a unique, incrementing version number automatically applied during the build process.

Does this workflow support building Expo dev clients for both iOS and Android environments?

Yes, this workflow supports building Expo dev clients for both iOS and Android. It covers configuring EAS development profiles and running builds on macOS for iOS as well as standard Android environments to test native code changes.