Expo app (SDK 53) loads in Tunnel mode but fails to open on my phone when using the normal connection

[paul15139]

Summary

I have a freshly initialized Expo SDK 53 and when I run npx expo start --tunnel, the app loads fine in Expo Go on my phone. But if I switch to npx expo start. Once I'm scanning the QR code in Expo Go, always “fails to load” (generic “Something went wrong” screen).

Things I've done:
Updated to the latest version of EAS CLI (npm i -g eas-cli)
Upgraded all dependencies to match SDK 53 (npx expo install expo@^53.0.0 --fix)
I've also checked for possible known issues (npx expo-doctor@latest) - No issues
Upgraded Expo SDK & core packages
Cleaned & reset the project environment

• Deleted node_modules, package-lock.json, .expo and .expo-shared folders.
• Re-ran npm install and npx expo start --clear to ensure a fresh cache.
  Tried LAN mode connectivity
  Ensured both my computer and mobile device are on the same Wi-Fi network and tried different networks.
  Metro Cache Clearing: Cleared the Metro Bundler cache using npx expo start --clear.
  Expo Go App Update: Updated the Expo Go app on my phone to the latest version.

I've updated the dependency package exclusion from validation and network checks but the issue persists. Everything was working fine on SDK 52 (previous Expo) but now there seems to be an issue I am not sure about

What platform(s) does this occur on?

No response

SDK Version

53

Environment

expo-env-info 1.3.3 environment info:
    System:
      OS: Windows 11 10.0.26100
    Binaries:
      Node: 22.14.0 - C:\Program Files\nodejs\node.EXE
      npm: 11.2.0 - C:\Program Files\nodejs\npm.CMD
    IDEs:
      Android Studio: AI-243.24978.46.2431.13208083
    npmPackages:
      expo: ~53.0.7 => 53.0.7
      expo-updates: ~0.28.12 => 0.28.12
      react: 19.0.0 => 19.0.0
      react-native: 0.79.2 => 0.79.2
    Expo Workflow: bare

Minimal reproducible example

n/a

[brentvatne]

this means that you're unable to reach the dev server on your computer from your phone. this is a common issue with public wifi / networks behind a NAT. https://docs.expo.dev/get-started/start-developing/#having-problems

[OkuraKenG]

Struggling with same issue, confused on why Expo Go worked fine with Expo 52 but breakes with Expo 53. If it helps found suggestion on Expo's Discord that led me to this solution-ish. I think Expo is displaying the wrong IP address in the CLI.

I compared the IP address given when running npx expo start and doing ipconfig.

Expo says it's serving on: exp://192.168.56.1:8081
My Ethernet adapter VirtualBox Host-Only Network: 192.168.56.1
My Wireless LAN adapter Wi-Fi: 192.168.1.119

Evidently Expo is showing VirtualBox's network and not Wi-Fi as expected. Expo 52 correctly shows Wi-Fi network.

Temporary solution?

A solution that seems to work for me personally was:

1. Run

ipconfig

2. Find the IPv4 address of Wireless LAN adapter Wi-Fi for you network:

   IPv4 Address. . . . . . . . . . . : 192.168.1.119

REACT_NATIVE_PACKAGER_HOSTNAME=192.168.1.119 npx expo start 

(replace with your actual IPv4 address)

This will generate the QR code that correctly generates the link for your network.

Extra Info

I think this is a visual issue within the CLI and not Expo binding with the wrong IP because, if I normally run:

npx expo start

Expo says they're serving on exp://192.168.56.1:8081 (Virtualbox) but...then manually go to exp://192.168.56.1:8081 it's being served there.

Edit this might be related to: #36526 and fixed by #36572
Double edit: lan-network@^0.1.5 does not resolve this/my issue but perhaps related. I'm not using a VPN.
Triple edit:
Running npx lan-network with VirtualBox enabled:

{
  "address": "192.168.56.1",
  "netmask": "255.255.255.0",
  "family": "IPv4",
  "mac": "0a:00:27:00:00:0d",
  "internal": false,
  "cidr": "192.168.56.1/24",
  "iname": "VirtualBox Host-Only Network",
  "gateway": null
}

Disabled VirtualBox (and ZeroTeir - which not running but still was an interface):

{
  "address": "192.168.1.119",
  "netmask": "255.255.255.0",
  "family": "IPv4",
  "mac": "dc:97:ba:c0:0b:0c",
  "internal": false,
  "cidr": "192.168.1.119/24",
  "iname": "Wi-Fi",
  "gateway": null
}

So possibly, an issue within ian-network package not properly resolving the Wi-Fi? I'm not running on public wifi or behind a NAT.

[paul15139]

Struggling with same issue, confused on why Expo Go worked fine with Expo 52 but breakes with Expo 53. If it helps found suggestion on Expo's Discord that led me to this solution-ish. I think Expo is displaying the wrong IP address in the CLI.

I compared the IP address given when running npx expo start and doing ipconfig.

Expo says it's serving on: exp://192.168.56.1:8081 My Ethernet adapter VirtualBox Host-Only Network: 192.168.56.1 My Wireless LAN adapter Wi-Fi: 192.168.1.119

Evidently Expo is showing VirtualBox's network and not Wi-Fi as expected. Expo 52 correctly shows Wi-Fi network.

Temporary solution?

A solution that seems to work for me personally was:

1. Run

ipconfig

2. Find the IPv4 address of Wireless LAN adapter Wi-Fi for you network:

   IPv4 Address. . . . . . . . . . . : 192.168.1.119

REACT_NATIVE_PACKAGER_HOSTNAME=192.168.1.119 npx expo start 

(replace with your actual IPv4 address)

This will generate the QR code that correctly generates the link for your network.

Extra Info

I think this is a visual issue within the CLI and not Expo binding with the wrong IP because, if I normally run:

npx expo start

Expo says they're serving on exp://192.168.56.1:8081 (Virtualbox) but...then manually go to exp://192.168.56.1:8081 it's being served there.

Edit this might be related to: #36526 and fixed by #36572 Double edit: lan-network@^0.1.5 does not resolve this/my issue but perhaps related. I'm not using a VPN. Triple edit: Running npx lan-network with VirtualBox enabled:

{
  "address": "192.168.56.1",
  "netmask": "255.255.255.0",
  "family": "IPv4",
  "mac": "0a:00:27:00:00:0d",
  "internal": false,
  "cidr": "192.168.56.1/24",
  "iname": "VirtualBox Host-Only Network",
  "gateway": null
}

Disabled VirtualBox (and ZeroTeir - which not running but still was an interface):

{
  "address": "192.168.1.119",
  "netmask": "255.255.255.0",
  "family": "IPv4",
  "mac": "dc:97:ba:c0:0b:0c",
  "internal": false,
  "cidr": "192.168.1.119/24",
  "iname": "Wi-Fi",
  "gateway": null
}

So possibly, an issue within ian-network package not properly resolving the Wi-Fi? I'm not running on public wifi or behind a NAT.

Thank you

Thanks so much!
This worked perfectly. after comparing the IP addresses from npx expo start and ipconfig, I realized Expo was showing the wrong IP as you've mentioned. Once I set REACT_NATIVE_PACKAGER_HOSTNAME to my Wi-Fi IPv4, everything worked as it should. Thanks once again!

[OkuraKenG]

Struggling with same issue, confused on why Expo Go worked fine with Expo 52 but breakes with Expo 53. If it helps found suggestion on Expo's Discord that led me to this solution-ish. I think Expo is displaying the wrong IP address in the CLI.
I compared the IP address given when running npx expo start and doing ipconfig.
Expo says it's serving on: exp://192.168.56.1:8081 My Ethernet adapter VirtualBox Host-Only Network: 192.168.56.1 My Wireless LAN adapter Wi-Fi: 192.168.1.119
Evidently Expo is showing VirtualBox's network and not Wi-Fi as expected. Expo 52 correctly shows Wi-Fi network.

Temporary solution?

A solution that seems to work for me personally was:

1. Run

ipconfig

2. Find the IPv4 address of Wireless LAN adapter Wi-Fi for you network:

   IPv4 Address. . . . . . . . . . . : 192.168.1.119

REACT_NATIVE_PACKAGER_HOSTNAME=192.168.1.119 npx expo start 

(replace with your actual IPv4 address)
This will generate the QR code that correctly generates the link for your network.

Extra Info

I think this is a visual issue within the CLI and not Expo binding with the wrong IP because, if I normally run:

npx expo start

Expo says they're serving on exp://192.168.56.1:8081 (Virtualbox) but...then manually go to exp://192.168.56.1:8081 it's being served there.
Edit this might be related to: #36526 and fixed by #36572 Double edit: lan-network@^0.1.5 does not resolve this/my issue but perhaps related. I'm not using a VPN. Triple edit: Running npx lan-network with VirtualBox enabled:

{
  "address": "192.168.56.1",
  "netmask": "255.255.255.0",
  "family": "IPv4",
  "mac": "0a:00:27:00:00:0d",
  "internal": false,
  "cidr": "192.168.56.1/24",
  "iname": "VirtualBox Host-Only Network",
  "gateway": null
}

Disabled VirtualBox (and ZeroTeir - which not running but still was an interface):

{
  "address": "192.168.1.119",
  "netmask": "255.255.255.0",
  "family": "IPv4",
  "mac": "dc:97:ba:c0:0b:0c",
  "internal": false,
  "cidr": "192.168.1.119/24",
  "iname": "Wi-Fi",
  "gateway": null
}

So possibly, an issue within ian-network package not properly resolving the Wi-Fi? I'm not running on public wifi or behind a NAT.

Thank you

Thanks so much! This worked perfectly. after comparing the IP addresses from npx expo start and ipconfig, I realized Expo was showing the wrong IP as you've mentioned. Once I set REACT_NATIVE_PACKAGER_HOSTNAME to my Wi-Fi IPv4, everything worked as it should. Thanks once again!

Glad it worked! Also try updating everything to the latest depedencies (npx expo install --fix). In that issue, lan-network@0.1.6 was updated fix a few issues. So that might provide a more permanent fix. See #36710 for more detail!

[dinakar17]

For me, it's the display issue. When I enter the URL manually in expo go app with the correct ipconfig address it's working fine.

[TanuiDev]

Tried to implementing the solution but doesn't work

[OkuraKenG]

Tried to implementing the solution but doesn't work

Make sure the lan-network package is running the latest version.

Also try running:

npx lan-network@latest --probe

In the output should say:

  "iname": "Wi-Fi",

If it does likely a different issue then this.