What problem does it solve? Testing custom native code in an Expo app requires a development client, and building, signing, and distributing one to physical devices involves complex EAS configuration and platform-specific tooling. ## Core Features & Use Cases - EAS Build Configuration: Set up eas.json with a development profile using developmentClient, autoIncrement, and remote app version sourcing. - TestFlight Distribution: Build iOS dev clients and submit them to TestFlight in a single command for team testing on physical devices. - Local Builds: Compile iOS and Android development clients locally and install them via simctl, ideviceinstaller, or adb. - Use Case: Your app adds a local Expo module with custom native code that Expo Go cannot run. Use this Skill to build a development client, push it to TestFlight, and connect it to your local Metro bundler for on-device testing. ## Quick Start Build an iOS development client with EAS and submit it to TestFlight so I can test my custom native code on my iPhone.