expo-dev-clientlisted

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. ## Important: When Development Clients Are Needed **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: - Local Expo modules (custom native code) - Apple targets (widgets, app clips, extensions) - Third-party native modules not in Expo Go **Try Expo Go first** with `npx expo start`. If everything works, you don't need a dev client. ## EAS Configuration Ensure `eas.json` has a development profile: ```json { "cli": { "version": ">= 16.0.1", "appVersionSource": "remote" }, "build": { "production": { "autoIncrement": true }, "development": { "autoIncrement": true, "developmentClient": true } }, "submit": { "production": {}, "development": {} } } ``` Key settings: - `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 ## Building for TestFlight Build iOS dev client and submit to TestFlight in one command: ```bash eas build -p ios --profile development --submit ``` This will: 1. Build the development client in the cloud 2. Automatically submit to App Store Connect 3. Send y