Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Next.js and React

Expo Go cannot load the app and shows Something went wrong

ErrorSomething went wrong

Short 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.

  • Applies to Expo SDK 5x, Expo CLI, Expo Go, Node.js 22
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 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 start
  2. 2Match what you see, then jump to its fix

    1. 1Expo 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. 2A physical iPhone refuses to open the project while an emulator works.iOS: Expo CLI and Expo Go use different accountsFix
    3. 3adb devices does not show the phone with the word device next to it.Android over USB: device not authorised or not listedFix

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 start

2Fix

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 --tunnel

3Verify

Scan the new QR code in Expo Go.

npx expo start --tunnel

Confirmed by docs.expo.dev

Did this fix it?

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 whoami

2Fix

Sign in on the computer, then sign in to Expo Go with the same account.

npx expo login

3Verify

Run whoami and compare it with the account shown in Expo Go.

npx expo whoami

Confirmed by docs.expo.dev

Did this fix it?

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 devices

2Fix

Reconnect the cable, accept any USB debugging prompt on the phone and run the check again until the phone shows as device.

adb devices

3Verify

Start the server again and open the project in Expo Go.

npx expo start

Confirmed by docs.expo.dev

Did this fix it?

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 fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.