expo-dev-client
Skill303 starsChanged 7 months agoMITView on GitHub
Build and distribute Expo development clients locally or via TestFlight
We split this skill into the rules it gives an agent
3 rules. 2 are common, 0 are distinctive, and 1 is very specific to this project.
2
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 8
Use EAS Build to create development clients for testing native code changes on physical devices.
- Very specific: line 23
Ensure eas.json has a development profile:
- Common: line 65
After receiving the TestFlight email:
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
{
"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 buildsautoIncrement: true- Automatically increments build numbersappVersionSource: "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:
eas build -p ios --profile development --submitThis will:
- Build the development client in the cloud
- Automatically submit to App Store Connect
- Send you an email when the build is ready in TestFlight
After receiving the TestFlight email:
- Download the build from TestFlight on your device
- Launch the app to see the expo-dev-client UI
- Connect to your local Metro bundler or scan a QR code
Building Locally
Build a development client on your machine:
# iOS (requires Xcode)
eas build -p ios --profile development --local
# Android
eas build -p android --profile development --localLocal builds output:
- iOS:
.ipafile - Android:
.apkor.aabfile
Installing Local Builds
Install iOS build on simulator:
# Find the .app in the .tar.gz output
tar -xzf build-*.tar.gz
xcrun simctl install booted ./path/to/App.appInstall iOS build on device (requires signing):
# Use Xcode Devices window or ideviceinstaller
ideviceinstaller -i build.ipaInstall Android build:
adb install build.apkBuilding for Specific Platform
# iOS only
eas build -p ios --profile development
# Android only
eas build -p android --profile development
# Both platforms
eas build --profile developmentChecking Build Status
# List recent builds
eas build:list
# View build details
eas build:viewUsing the Dev Client
Once installed, the dev client provides:
- Development server connection - Enter your Metro bundler URL or scan QR
- Build information - View native build details
- Launcher UI - Switch between development servers
Connect to local development:
# Start Metro bundler
npx expo start --dev-client
# Scan QR code with dev client or enter URL manuallyTroubleshooting
Build fails with signing errors:
eas credentialsClear build cache:
eas build -p ios --profile development --clear-cacheCheck EAS CLI version:
eas --version
eas updateOther versions13 projects use a version of this.
Word for word · 9
- openai/plugins★ 7.4k100% same
- CherryHQ/cherry-studio-app★ 4k100% same
- kingstinct/react-native-healthkit★ 719100% same
- ruizrica/agent-pi★ 274100% same
- robinebers/skills★ 48100% same
- PIXARTSeu/Synapse★ 9100% same
- xfstudio/skills★ 9100% same
- Samueladewole/claude-skills★ 0100% same
- Ultimate-Alchemy/claude-skills★ 0100% same
Edited · 4
- arcboxlabs/linkcode★ 14767% same
- deonmenezes/mobile-app-skill★ 464% same
- mahik504/orchestra-workflow★ 163% same
- patinaproject/skills★ 163% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- expo-tailwind-setupSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

