You may choose to install directly to your device (the -device flag with npx expo run:, or by selecting it in an IDE) or to use internal distribution, or TestFlight / Google Play.I've straggled with similar issue, I managed to solve it following several steps found on the web, and tweaking a bit: If you have expo-dev-client installed in your project, you will need to build the 'Release' configuration/variant ( -configuration Release for iOS and -variant release for Android). You can create standalone builds in the same way as development builds - locally with npx expo run: -device, with Xcode or Android Studio, or remotely with EAS Build. Running a project as a standalone appīoth Expo Go and development builds include a user interface that is convenient for development, but that you would not use in a production release of your app.

Refer to the Getting Started guide for development builds to learn how to create and run it on your device. Development builds can be created locally with npx expo run: -device, with Xcode or Android Studio, or remotely with EAS Build.

Running a project with a development buildĮxpo Go is for quick experimentation, when it's time to build an app you can create development builds (for example, to add custom native code), the process for loading the project remains mostly the same but the mechanism to get the build on your device is different. You may want to install a simulator/emulator to speed up development if 'Tunnel' is required for accessing your machine from another device on your network. Using the 'Tunnel' connection type will make app reloads considerably slower than on 'LAN' or 'Local', so it's best to avoid tunnel when possible.

Expo android studio