expo-dev-client

Build custom Expo development clients for testing native code on physical devices via EAS Build or locally. 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. Only create development clients when your app requires custom native code. Most apps work fine in Expo Go. You need a dev client ONLY when using: Try Expo Go first with npx expo start . If everything works, you don't need a dev client. Ensure eas.json has a development profile: Key settings: Build iOS dev client and submit to TestFlight in one command: This will: After receiving the TestFlight email: Build a development client on your machine: Local builds output: Install iOS build on simulator: Install iOS build on device (requires signing): Install Android build: Once installed, the dev client provides: Connect to local development: Build fails with signing errors: Clear build cache: Check EAS CLI version: - Only needed when using custom native modules, Apple targets (widgets, app clips), or third-party native code not in Expo Go; try Expo Go first with npx expo start - Supports cloud builds with automatic TestFlight submission or local builds on your machine, outputting .ipa (iOS) or .apk / .aab (Android) files - Requires eas.json configuration with a development profile that sets...