Fix "not supported in Expo Go" with a dev build | Vovy
Create an Expo development build, your own custom version of Expo Go, so native packages like payments, maps or Bluetooth work while you build.
My app needs a package that doesn't work in Expo Go. Make a dev build
How it works
- Confirm the error: Vovy reads the red screen, like a missing native module error, and explains that the package ships native code Expo Go does not include.
- Install expo-dev-client: Vovy runs npx expo install expo-dev-client, which turns your project into its own dev app with a launcher and debug menu.
- Build for the Simulator: Vovy runs npx expo run:ios, which builds locally with Xcode and installs it on the Simulator. No Apple account needed for this part.
- Build for your phone: For a real iPhone, Vovy runs eas build --profile development and registers your device, which needs a paid Apple account.
- Connect and keep coding: Vovy starts npx expo start and opens your dev build. A card explains when you need to rebuild: only when native packages change.
What you provide
- Your Expo project
- Xcode installed
- A paid Apple account for real devices
What you get
- A development build with your native packages
- The app on Simulator and phone
- A rule for when to rebuild
FAQ
Do I stop using Expo Go completely?
For this project, yes. The dev build works the same way but includes your native code.
Do I need to rebuild after every change?
No. JavaScript changes still reload instantly. Rebuild only when you add or update a native package.
Does this cost money?
Local Simulator builds are free. Cloud builds use your EAS plan's build allowance.
Related tasks
All tasksLoading...