expo-dev-client

Automate building and distributing Expo development clients to TestFlight.

Updated Sep 7, 2024
One-click install
npx skills add https://github.com/Asylcreek/home-manager --skill expo-dev-client-asylcreek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-dev-client
Source: https://github.com/Asylcreek/home-manager/tree/main/dots/agents/skills/expo-dev-client
Command: npx skills add https://github.com/Asylcreek/home-manager --skill expo-dev-client-asylcreek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Development teams often need a native-like Expo client to test custom native modules or Apple platform features without publishing to production. This Skill guides you through configuring, building, and distributing expo dev clients locally or via TestFlight, enabling faster feedback loops between code changes and QA.

Core Features & Use Cases

  • Create development clients to test local native code changes in a real device or simulator.
  • Build and deliver dev clients to TestFlight for broader testing and stakeholder demos.
  • Integrate with EAS Build profiles to control versioning, signing, and automatic submission workflows.

Quick Start

Run eas build -p ios --profile development --submit to create and submit the Expo development client to TestFlight.

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 development client for testing custom native modules?

To build an Expo development client for custom native modules, you configure an EAS project with a development profile and run a build command targeting your specific platform profile. This creates a custom client replacing Expo Go for native code testing.

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

You need a custom Expo dev client when your project includes local native modules, Apple platform targets, or third-party native modules not supported by Expo Go. It enables testing native code changes on real devices or simulators.

How do I submit an Expo dev client to TestFlight for QA testing?

To submit an Expo dev client to TestFlight, run the EAS build command with the development profile and submit flag for iOS. This automates the build, signing, and distribution process for broader stakeholder testing.

Do I need a configured EAS project to distribute Expo dev clients?

Yes, distributing Expo dev clients requires a configured EAS project with a development profile, credentials, and platform access. This setup manages versioning, signing, and automatic submission workflows for your builds.

Can I use EAS Build profiles to control versioning for Expo development clients?

Yes, you can integrate EAS Build profiles to control versioning, signing, and automatic submission workflows for Expo development clients. This allows customized build configurations tailored to your testing and distribution needs.

What are the limitations of using Expo Go for testing local native code changes?

Expo Go cannot test local native code changes, Apple platform targets, or third-party native modules not included in its standard runtime. Building a custom Expo dev client via EAS is required to bypass these limitations and test native features.