Expo Go cannot load the app and shows Something went wrong
Something went wrongShort answer
Expo Go could not reach the dev server or was not allowed to open the project. Start Expo with --tunnel when the network blocks local connections. On iOS, Expo CLI and Expo Go must use the same account. On Android over USB, adb devices must list the device.
Fix it fast
1Find out which cause you have
Check which account the CLI uses and whether the dev server runs. The reply shows whether the sign-in or the network is at fault.
npx expo whoami npx expo start2Match what you see, then jump to its fix
- 1
Expo starts, the QR code appears, but the phone never loads the bundle. Common on office, guest and campus Wi-Fi.The network blocks the local connectionFix - 2
A physical iPhone refuses to open the project while an emulator works.iOS: Expo CLI and Expo Go use different accountsFix - 3
adb devices does not show the phone with the word device next to it.Android over USB: device not authorised or not listedFix
- 1
What does the error look like?
Something went wrong
Cause 1 of 3
The network blocks the local connection
1Check
By default the project is served over the local network. Restrictive networks, firewalls and some emulator setups block that.
npx expo start2Fix
Serve through a tunnel. It works from any device with internet access, but it is slower and the URL is public.
npm i -g @expo/ngrok
npx expo start --tunnel3Verify
Scan the new QR code in Expo Go.
npx expo start --tunnelConfirmed by docs.expo.dev
Cause 2 of 3
iOS: Expo CLI and Expo Go use different accounts
1Check
A physical iOS device opens a project from a dev server only when both sides are signed in to the same Expo account.
npx expo whoami2Fix
Sign in on the computer, then sign in to Expo Go with the same account.
npx expo login3Verify
Run whoami and compare it with the account shown in Expo Go.
npx expo whoamiConfirmed by docs.expo.dev
Cause 3 of 3
Android over USB: device not authorised or not listed
1Check
The Expo docs say a USB phone must appear in this list with the word device next to it.
adb devices2Fix
Reconnect the cable, accept any USB debugging prompt on the phone and run the check again until the phone shows as device.
adb devices3Verify
Start the server again and open the project in Expo Go.
npx expo startConfirmed by docs.expo.dev
How do I stop it coming back?
- Run npx expo whoami at the start of a session if you use several Expo accounts.
- Keep --tunnel as the fallback on networks you do not control.
- Use a development build when the app needs native modules Expo Go does not include.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Web apps
tsconfig rejects allowImportingTsExtensions
An error that allowImportingTsExtensions needs noEmit or emitDeclarationOnly
allowImportingTsExtensions lets files import each other with .ts or .tsx extensions, and TypeScript only allows it together with noEmit or emitDeclarationOnly.
2 causes, each with a fixWeb apps
Apollo Server rejects a request as a potential CSRF
HTTP 400 Bad Request from the GraphQL endpoint
Apollo Server's CSRF prevention is on by default.
3 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
AxiosError Network Error with code ERR_NETWORK in a React app
Network Error
ERR_NETWORK means the request produced no readable response.
4 causes, each with a fixWeb apps
Axios get works with a URL string but ignores the object passed as the second argument
The server log shows a GET with no query string
axios.get takes a URL and an optional config object.
3 causes, each with a fixWeb apps
Can't resolve '../axios' in a React project
Module not found: Error: Can't resolve '../axios'
A path that starts with ./ or ../ is a file path, not the axios package.
3 causes, each with a fix