expo-dev-client
สร้าง Expo development clients แบบกำหนดเองสำหรับทดสอบโค้ดเนทีฟบนอุปกรณ์จริงผ่าน EAS Build หรือในเครื่อง จำเป็นเมื่อใช้โมดูลเนทีฟที่กำหนดเอง, เป้าหมาย Apple (วิดเจ็ต, app clips), หรือโค้ดเนทีฟของบุคคลที่สามที่ไม่มีใน Expo Go; ลองใช้ Expo Go ก่อนด้วย npx expo start รองรับการ build บนคลาวด์พร้อมส่ง TestFlight อัตโนมัติหรือ build ในเครื่องบนเครื่องของคุณ โดยสร้างไฟล์ .ipa (iOS) หรือ .apk / .aab (Android) ต้องกำหนดค่า eas.json ด้วยโปรไฟล์ development ที่ตั้งค่า...
npx skills add https://github.com/expo/skills --skill expo-dev-clientUse 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.
Free locally; cloud builds are paid.
expo-dev-clientitself is open source and building locally is free. Building or distributing via EAS Build/TestFlight uses your EAS plan's build minutes and needs a paid Apple Developer account for device/TestFlight distribution. See https://expo.dev/pricing.
Important: When Development Clients Are Needed
Development clients are the recommended setup for any real or production app. Expo Go is a playground for learning and quick experiments with the native libraries it bundles; most apps outgrow it and move to a development client. See Expo Go vs. development builds for the full reasoning.
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
- Config plugins, or testing remote push notifications and App/Universal Links
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:
npx --yes eas-cli@latest build -p ios --profile development --submit
This 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)
npx --yes eas-cli@latest build -p ios --profile development --local
# Android
npx --yes eas-cli@latest build -p android --profile development --local
Local 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.app
Install iOS build on device (requires signing):
# Use Xcode Devices window or ideviceinstaller
ideviceinstaller -i build.ipa
Install Android build:
adb install build.apk
Building for Specific Platform
# iOS only
npx --yes eas-cli@latest build -p ios --profile development
# Android only
npx --yes eas-cli@latest build -p android --profile development
# Both platforms
npx --yes eas-cli@latest build --profile development
Checking Build Status
# List recent builds
npx --yes eas-cli@latest build:list
# View build details
npx --yes eas-cli@latest build:view
Using 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 manually
When you launch the dev client yourself to screenshot or drive it, skip the onboarding sheet, the dev menu at launch, and the Tools button. On SDK 58+, Expo CLI does this for launches it starts from a non-interactive shell; for a URL you open yourself, use <scheme>://?__expo_url=<encoded dev server URL>&__expo_disable_onboarding=1&__expo_disable_fab=1&__expo_disable_auto_launch=1. On SDK 57 and earlier, launch the iOS app with the -EXDevMenu* launch arguments, and on Android open <scheme>://expo-development-client/?url=<encoded dev server URL>&disableOnboarding=1&disableFab=1&disableAutoLaunch=1. See ../expo-overview/references/launch-without-dev-menu.md for the exact commands.
Troubleshooting
Build fails with signing errors:
npx --yes eas-cli@latest credentials
Clear build cache:
npx --yes eas-cli@latest build -p ios --profile development --clear-cache
Check EAS CLI version:
npx --yes eas-cli@latest --version
Submitting Feedback
You can voluntarily report errors, misleading or outdated information in this skill, so Expo can improve it:
npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-dev-client" --message "<actionable feedback>"
Use --category agent-cli for a problem with the agent CLI, and --category evals when an agent repeatedly fails at an Expo task. Run feedback --help for subjects and the data that the command sends.
Each report goes to Expo with project and environment details. Show the user the message, and send it only if the user agrees. If you cannot ask the user, do not send it. Do not include secrets or personal data.