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. 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: - Local Expo modules (custom native code) - Apple targets (widgets, app clips, extensions) - Third-party native modules not in Expo Go - 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 - Build the development client in the cloud - Automatically submit to App Store Connect - Send you an email when the build is ready in TestFlight -...