Building a react native app in WSL2

rearct-native-app-in-wsl2.md

Building a react native app in WSL2

Install, build and debug a react native app in WSL2 (Windows Subsystem for Linux) and Ubuntu.

• Install tools in Windows
• Install tools in WSL2
• Connect to android hardware device from WSL2
• Connect to android virtual device in Windows
  • Start android virtual device in Windows
  • Start adb server in Windows
  • Enable access to adb server from WSL2
  • Enable access to metro bundler from Windows
• Connect to Windows Subsystem for Android
• Create react native app in WSL2
• Build app in WSL2
• Debug app in Visual Studio Code from WSL2

Install tools in Windows

• Install WSL2 and Ubuntu, see here
• Install Android Studion, see here
• Install Viusal Studio Code, see here

Install tools in WSL2

• Install java-8-openjdk in WSL2 (sudo apt-get install openjdk-8-jre)
• Install Android SDK cmdline tools in WSL2, see here and adjust directory structure, see here
• Install nodejs in WSL2, see here

Set environment variables in .profile or .bash_profile

export ANDROID_HOME=/home/xxx/Android/cmdline-tools/latest
export ANDROID_SDK_ROOT=/home/xxx/Android

PATH=$PATH:$ANDROID_SDK_ROOT/platform-tools
PATH=$PATH:$ANDROID_HOME/bin

export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64

Connect to android hardware device from WSL2

To debug on a hardware device connect to android device via usbip from WSL2 (thanks to @cjshearer):

• Connect USB device to WSL
• Enable USB debugging on the device

Connect to android virtual device in Windows

To debug on a virtual device create a virtual device (e.g. Nexus_5X_API_29) in windows with Android Virtual Device Manager from Android Studio.

Start android virtual device in Windows

Start Android virtual device (e.g. Nexus_5X_API_29) in windows

"C:\Program Files (x86)\Android\android-sdk\emulator\emulator.exe" -avd Nexus_5X_API_29

Start adb server in Windows

adb kill-server
adb -a nodaemon server start

Change firewall rule for adb.exe on first usage in Defender Popup or with Windows Defender Firewall allowing access for the public profile, because the vEthernet (Wsl) adapter belongs to the public profile

Enable access to adb server from WSL2

Set environment variable to access adb server, WSL_HOST is ip of vEthernet (WSL) interface in windows

export WSL_HOST=$(tail -1 /etc/resolv.conf | cut -d' ' -f2)
export ADB_SERVER_SOCKET=tcp:$WSL_HOST:5037

Somtimes adb crashes using the environment variable config. One solution is to use socat (thanks to @tuanna1601).

Unset the environment variable if necessary.

unset ADB_SERVER_SOCKET

Install socat (eg. sudo apt-get install socat). Socat relays the requests from wsl2 to windows using the following command:

socat -d -d TCP-LISTEN:5037,reuseaddr,fork TCP:$(cat /etc/resolv.conf | tail -n1 | cut -d " " -f 2):5037

Enable access to metro bundler from Windows

The metro bundler is running in WSL2, listening on port 8081. Windows 10 version 2004 brings network forwarding from WSL2 to Windows. So the app can connect to the metro bundler from the emulator via Windows localhost.

Sometimes there are problems with the network forwarding. A work around is to use the following script.

WSL_CLIENT is ip of WSL2.

iex "netsh interface portproxy delete v4tov4 listenport=8081 listenaddress=127.0.0.1" | out-null;
$WSL_CLIENT = bash.exe -c "ifconfig eth0 | grep 'inet '";
$WSL_CLIENT -match '\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}';
$WSL_CLIENT = $matches[0];
iex "netsh interface portproxy add v4tov4 listenport=8081 listenaddress=127.0.0.1 connectport=8081 connectaddress=$WSL_CLIENT"

Connect to Windows Subsystem for Android

To debug the app running on Windows Subsystem for Android (WSA).

Install Windows Subsystem for Android.

Start adb server in Windows.

Enable access to adb server from WSL2.

Enable access to metro bundler from Windows Subsystem for Android

The metro bundler is running in WSL2, listening on port 8081.

To enable access from WSA to WSL2, configure adb reverse port forwarding on WSA.

Connect to the WSA via 127.0.0.1:58526 and execute adb reverse.

adb connect 127.0.0.1:58526
adb reverse tcp:8081 tcp:8081 

Create react native app in WSL2

npx react-native init AwesomeProject

Build app in WSL2

Add paraameter in file proguard-rules.pro to ignore okhttp3 warnings

-dontwarn okhttp3.internal.platform.*

Start metro JavaScript bundler and bind to an ipv4 address to enable port forwarding to windows

npx react-native start --host 127.0.0.1

Build app, set device as parameter deviceId from result of adb devices

• deviceId emulator: emulator-5554
• deviceId WSA: 127.0.0.1:58526

npx react-native run-android --variant=debug --deviceId <deviceId>

Debug app in Visual Studio Code from WSL2

Start vs code in WSL2

code .

and install extensions for VS Code

• Remote - WSL
• React Native Tools

VS Code UI runs in windows and the VS Code Server runs in WSL2, see here

Add a launch configuration in file launch.json with specified type and request

"name": "Attach to packager",
"cwd": "${workspaceFolder}",
"type": "reactnative",
"request": "attach"

Build app, attach to packager and start debugging, see here.

Is there a complete version of this guide updated for the latest changes?
It's been 2 days now playing around this, no LUCK!
tried everything, either gives an error for expecting the android tools folder to be in some other place or for unaccepted licenses or can't connect to adb or there are so many other things ... please kindly guide me through the updated process.

Windows 10 20H2 19042.804
WSL 2 Ubuntu 20 LTS
Android Studio in Windows ...

I am facing all kinds of problems ... please please help

Is there a complete version of this guide updated for the latest changes?
It's been 2 days now playing around this, no LUCK!

@ViperTechnologies-RnD Hey man, look at my post on the gist, I made a guide and some people were successful, maybe I can help you, it's in Brazilian Portuguese.

https://gist.github.com/georgealan/353a548814fe9b82a3a502926c7a42c6

I followed your tutorial but i stuck with

Unable to load script.Make sure you are either running a Metro server or that your bundle 'index.android.bundle' is packaged correctly for release

how I resolve this issue

@romonsalve hmm, still trying with expo and can't specify the deviceId
Another speculation is that expo is trying the port of the deviceId number. For emulator-5554 it is trying the 5554 port, and not the port that we allow to connect to Windows (5037)

Did you manage to solve this? When running adb devices I do see my Emulator, but Expo just says Connection Refused.

@seklyza No, just started using tunnel mode or private network ip

I was unable to connect to the Metro Bundler from the emulator. I was getting "Unable to load script".

I get it to work by disabling the firewall and omitting the --host part when running npx react-native start.

Despite setting ADB_SERVER_SOCKET, my gradle task is trying to start adb on WSL. It hangs at 99% and the app is not installed on the emulator. Anyone else hitting this?

12:56:53 D/ddms: Launching '/home/davisj/Android/Sdk/platform-tools/adb start-server' to ensure ADB is running.
12:56:53 D/ddms: '/home/davisj/Android/Sdk/platform-tools/adb start-server' succeeded
12:56:53 I/DeviceMonitor: adb restarted
12:56:54 D/DeviceMonitor: Opening adb connection
12:56:54 E/DeviceMonitor: Unable to open connection to: localhost/127.0.0.1:5037, due to: java.net.ConnectException: Connection refused
12:56:54 E/DeviceMonitor: Connection attempts: 1570

I was able to get past this by using socat. Looks like WSL port forwarding wasn't working as expected although I was able to talk to the adb server on Windows from the command line.

If you're going to use socat, I would suggest using adb -a -P 5037 nodaemon server when running adb on windows, before using socat -d -d TCP-LISTEN:5037,reuseaddr,fork TCP:$(cat /etc/resolv.conf | tail -n1 | cut -d " " -f 2):5037 on wsl.

When forwarding the metro bundler ports I had to use the following to open a firewall on windows:

• $WSL_CLIENT = bash.exe -c "ip addr show eth0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}'"
• iex "netsh interface portproxy add v4tov4 listenport=8081 listenaddress=127.0.0.1 connectport=8081 connectaddress=$WSL_CLIENT"

C:\Users\<me>\AppData\Local\Android\sdk\tools\emulator.exe

This work for me to ubuntu 20.04.
script to get windows ip and wls ip and foward port and ip
and to display right ip on expo set this

REACT_NATIVE_PACKAGER_HOSTNAME=your_windows_host_ip
ex wsl terminal:
export REACT_NATIVE_PACKAGER_HOSTNAME=192.168.38.16

#//wsl2Unlock.ps1
$windowsIp = bash -c "ip addr show eth0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}'"
$wslIp = wsl ~ -d Ubuntu-20.04 -e ip addr show eth0
$found = $wslIp -match '(?<=inet\s)\d+(\.\d+){3}';

if ( $found ) {
  $found[0] -match '\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}'
  $wslIp = $matches[0]
}
else {
  Write-Output "The Script Exited, the ip address of WSL 2 cannot be found";
  exit;
}
Write-Output $wslIp
Write-Output $windowsIp

# show all portproxy
Invoke-Expression "netsh interface portproxy show v4tov4"

#remove all 
Invoke-Expression "netsh int portproxy reset all"

# Remove Firewall Exception Rules
Invoke-Expression "Remove-NetFireWallRule -DisplayName 'WSL 2 Firewall Unlock' ";

# [Ports]
# All the ports you want to forward separated by coma
$ports = @(19000, 19001, 19002, 19003, 19004, 19005, 19006);
$ports_a = $ports -join ",";


# #adding Exception Rules for inbound and outbound Rules
Invoke-Expression "New-NetFireWallRule -DisplayName 'WSL 2 Firewall Unlock' -Direction Outbound -LocalPort $ports_a -Action Allow -Protocol TCP";
Invoke-Expression "New-NetFireWallRule -DisplayName 'WSL 2 Firewall Unlock' -Direction Inbound -LocalPort $ports_a -Action Allow -Protocol TCP";

for ( $i = 0; $i -lt $ports.length; $i++ ) {
  $port = $ports[$i];
  Invoke-Expression "netsh interface portproxy add v4tov4 listenport=$port listenaddress=$windowsIp connectport=$port connectaddress=$wslIp";
}

I always have to execute the Metro Bundler Forwarding to connect to react-native... anyone knows why? Is there a definitive way to do this?

I also have to execute the Metro Bundler Forwarding on startup before npm start.
I created a simple script executable from WSL to start the forwarding, along with starting the adb server.
I thought I'd share it here:

• some/wsl/folder/start_adb.sh

#!/usr/bin/env sh

winpwd=$(printf "%s" "$PWD" | sed 's/\//\\/g')
powershell.exe Start-Process -Verb runas powershell.exe -ArgumentList "\"-NoExit -ExecutionPolicy Bypass \\\\wsl\$\\Ubuntu$winpwd\\proxy_adb.ps1\""

• some/wsl/folder/proxy_adb.ps1

# Forward metro
iex "netsh interface portproxy delete v4tov4 listenport=8081 listenaddress=127.0.0.1" | out-null;
$WSL_CLIENT = bash.exe -c "ip addr show eth0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}'";
$WSL_CLIENT -match '\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}';
$WSL_CLIENT = $matches[0];
iex "netsh interface portproxy add v4tov4 listenport=8081 listenaddress=127.0.0.1 connectport=8081 connectaddress=$WSL_CLIENT"
# Start adb server
adb kill-server
adb -a nodaemon server start

Simply launch the start_adb script, it will prompt you for admin rights. Remember to add adb to windows path.

New Method for Android

1. Install the sdk manager (without needing android studio).

2. For physical devices: usbipd-win can now be used to expose your android device (or any usb device) directly in WSL2. I've tested and used this to deploy react-native apps to my android device. In addition, this method will work with debugging tools like Flipper, as it doesn't rely on a Windows ADB server.

See the discussion here if you have any issues getting it working for ADB: dorssel/usbipd-win#60

@cjshearer thank you very much, got it work on my box

@cjshearer @bergmannjg i'm trying to connect my Android device from WSL2. Everything is fine with usbipd-win, even my device shows up in "adb devices" command (WSL2). But i get an error when i try "npx react-native run-android"

error Failed to install the app. Make sure you have the Android development environment set up: https://facebook.github.io/react-native/docs/getting-started.html#android-development-environment. Run CLI with --verbose flag for more details.Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081

Also, i've tried with "npx react-native run-android --deviceId=", still i get an error, but it says

error Failed to build the app. Run CLI with --verbose flag for more details. Error: Command failed: ./gradlew build -x lint

How do you guys make it work?
My last last last step is use Ubuntu directly (dual boot alongside Windows).

@bergmannjg By the way, i've also tried connecting android virtual device in Windows from WSL2, and i also get the second error.

@RakaDoank what is the error msg of

./gradlew app:installDebug -PreactNativeDevServerPort=8081

@bergmannjg i get

bash: ./gradlew: No such file or directory

i only found out the error after you asked. So, i tried gradle wrapper first and run the ./gradlew command again, then i get this new error

Project 'app' not found in root project 'myProject'

I'm sorry, this is probably not a WSL issue.

Has anyone have an updated version of the guide? Been stuck on different places.

ERROR ON:

adb kill-server
adb -a nodaemon server start

emulator-5554: already offline
what does this mean?

For those struggling with Expo with the error Couldn't start project on Android: could not connect to TCP port 5554: Connection refused

I'm no expert, but debugging things a little with variables EXPO_DEBUG=1 and ADB_TRACE=adb, I found out that expo start was executing the command adb -s emulator-5554 emu avd name , and somehow this command from the Ubuntu side didn't work (maybe someone here can help fix this), but the adb running on Windows could run that command from Ubuntu with adb.exe.

So, I successfully overrode that with sudo ln -s /mnt/c/Android/Sdk/platform-tools/adb.exe ~/Android/sdk/platform-tools/adb after backing up the original ubuntu adb executable (just fix that path with your windows adb path and your possible custom ubuntu adb path)

I did that only when running the expo start command and all worked smoothly (until now at least)

If anyone can help us to find out why adb on ubuntu side cannot access the emulator, I would appreciate it (even when adb devices runs normally and lists the device)

---

PS: all worked without

• any netsh interface portproxy or
• any adb reverse or
• firewall rule to allow WSL ports (only rule to allow adb program)
• admin rights command execution
• socat alternative

But I used the variables below:

export WSL_HOST=$(tail -1 /etc/resolv.conf | cut -d' ' -f2)
export ADB_SERVER_SOCKET=tcp:$WSL_HOST:5037
export ADB_TRACE=adb
export EXPO_DEBUG=1
export ANDROID_SERIAL=emulator-5554
export REACT_NATIVE_PACKAGER_HOSTNAME=$(ip addr show eth0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}')

and...

• used same version of platform-tools on both windows and ubuntu
• used adb kill-server && adb -a -P 5037 nodaemon server start on Windows side after emulator loaded

versions...

• Windows 11 and Ubuntu 20.04
• expo-cli 5.4.3
• last version of node and npm (v16.15.0 - v8.8.0)
• emulator running avd Pixel_4_API_30 with Google APIs
• usb debug mode enabled on emulator
• adb version 1.0.41 and platform-tools 33.0.1

For those struggling with Expo with the error Couldn't start project on Android: could not connect to TCP port 5554: Connection refused

I'm no expert, but debugging things a little with variables EXPO_DEBUG=1 and ADB_TRACE=adb, I found out that expo start was executing the command adb -s emulator-5554 emu avd name , and somehow this command from the Ubuntu side didn't work (maybe someone here can help fix this), but the adb running on Windows could run that command from Ubuntu with adb.exe.

So, I successfully overrode that with sudo ln -s /mnt/c/Android/Sdk/platform-tools/adb.exe ~/Android/sdk/platform-tools/adb after backing up the original ubuntu adb executable (just fix that path with your windows adb path and your possible custom ubuntu adb path)

I did that only when running the expo start command and all worked smoothly (until now at least)

If anyone can help us to find out why adb on ubuntu side cannot access the emulator, I would appreciate it (even when adb devices runs normally and lists the device)

PS: all worked without

• any netsh interface portproxy or
• any adb reverse or
• firewall rule to allow WSL ports (only rule to allow adb program)
• admin rights command execution
• socat alternative

But I used the variables below:

export WSL_HOST=$(tail -1 /etc/resolv.conf | cut -d' ' -f2)
export ADB_SERVER_SOCKET=tcp:$WSL_HOST:5037
export ADB_TRACE=adb
export EXPO_DEBUG=1
export ANDROID_SERIAL=emulator-5554
export REACT_NATIVE_PACKAGER_HOSTNAME=$(ip addr show eth0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}')

and...

• used same version of platform-tools on both windows and ubuntu
• used adb kill-server && adb -a -P 5037 nodaemon server start on Windows side after emulator loaded

versions...

• Windows 11 and Ubuntu 20.04
• expo-cli 5.4.3
• last version of node and npm (v16.15.0 - v8.8.0)
• emulator running avd Pixel_4_API_30 with Google APIs
• usb debug mode enabled on emulator
• adb version 1.0.41 and platform-tools 33.0.1

Thanks, @luizwhite , it really helped. It was the easiest one I found on the internet so far 😊 . Let's wait for someone who got some ideas about it.

@luizwhite thanks a lot! Your solution works like a charm. That's what I was searching for. 🍺

For the proxy to work properly with socat. still need to run npx react-native start --host 0.0.0.0 without 127.0.0.1

Wonderful!

I had the experience of successfully setting up and running react native applications on WSL + Windows AVD emulator with using socat command. But recently I moved to a new computer and did everything as it was on the last machine, only with a newer SDK and tools versions and after running the adb devices command on the WSL, I get this error
adb: failed to check server version: protocol fault (couldn't read status): Success
while windows adb server and socat command run successfully.
And when I kill the socat process, adb devices command works well, but without seeing the windows emulator for sure.
All SDK and tool versions are the same on Windows and WSL.
Can someone help me figure out what it is?

socat log for the adb devices query

2022/07/26 17:28:34 socat[2129] N opening connection to AF=2 172.17.96.1:5037
2022/07/26 17:29:07 socat[2129] E connect(5, AF=2 172.17.96.1:5037, 16): Connection timed out
2022/07/26 17:29:07 socat[2129] N exit(1)

upd: solved by adding the firewall rule for adb.exe

and adjust directory structure, see here

Wish this section was more clear.

I had problems using expo and the solution @luizwhite gave worked for me.

So, I successfully overrode that with sudo ln -s /mnt/c/Android/Sdk/platform-tools/adb.exe ~/Android/sdk/platform-tools/adb after backing up the original ubuntu adb executable (just fix that path with your windows adb path and your possible custom ubuntu adb path)

However, I'm concerned there could be any kind of performance issues due to WSL2 accessing Windows memory. It would be great if anyone could point out if it could become an issue going forward.

@luizwhite I was able to connect the emulator. However when I run npx expo start --android I get this error. The Expo-*.apk exists in the directory. Any idea?

NVM, I was able to install the apk with: adb install Exponent-2.28.6.apk.

Having issue with npx expo start
Getting error: could not connect to TCP port 5554: Connection refused.

Set environment variables

export WSL_HOST=$(tail -1 /etc/resolv.conf | cut -d' ' -f2)
export ADB_SERVER_SOCKET=tcp:$WSL_HOST:5037
export ANDROID_SERIAL=emulator-5554
export REACT_NATIVE_PACKAGER_HOSTNAME=$(ip addr show eth0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}')

Starting adb in Windows, emulator was started before

> adb -a nodaemon -P 5037 server start
adb.exe I 05-24 10:56:45 20016 16472 auth.cpp:416] adb_auth_init...
adb.exe I 05-24 10:56:45 20016 16472 auth.cpp:152] loaded new key from 'C:\Users\***\.android\adbkey' with fingerprint A7A3F84B061B063E11EFD5034A7C67ED92AA52C7AA569BE5BEE9BD597E01DDB2
adb.exe I 05-24 10:56:45 20016  5140 transport.cpp:335] emulator-5554: read thread spawning
adb.exe I 05-24 10:56:45 20016 17240 transport.cpp:307] emulator-5554: write thread spawning
adb.exe I 05-24 10:56:45 20016 16472 adb.cpp:173] emulator-5554: already offline

adb in WSL

> adb devices
List of devices attached
emulator-5554   device

> adb shell
emu64xa:/ $

It's ridiculous how complicated it is to set up a dev environment

I give up, it's better to learn a native language for mobile or something.

I give up, it's better to learn a native language for mobile or something.

Or just don't use wsl2.
I give up wsl2...

There is a typo in the file name. rearct-native-app-in-wsl2.md -> react-native-app-in-wsl2.md.

I give up, it's better to learn a native language for mobile or something.

Or just don't use wsl2. I give up wsl2...

yes, you're right

@sprngLf @osherz this is the same conclusion I came to. WSL is awesome...unless you need usb. I abandoned Windows on my work machine because react-native dev, while possible on WSL, is just too much maintenance on top of an already very complicated framework.

I didn't follow the guide and I didn't need to do any extra config to make the react native environment work in WSL and testing on a physical device or WSA (Windows Subsystem for Android).

Just on physical device I enabled wifi debugging and on WSL:

adb pair <ip:port of physical device connected on the same network of the host computer that is running the WSL>
adb connect <ip:port>

npx react-native start
npx react-native run-android

After the build process then the app started both on the physical device and also on the WSA

@vagnerlandio Thanks for that solution, i was trying to not leave wsl because i so greate for me, and my workspace is all around windows, so trying to find a solution to not use a device connected to my pc it was hard. To all who wants to usea a emulator, just install the WSA (Windows Subsystem for Android) and having the command line tools from android installed on WSL, you just do:

adb connect <ip:port> (try with 127.0.0.1:58526 if isn't working use yout local ip ex: 10.5.0.2:58526)

The port you can find it on the WSA > Advance Settings > Developer mode

Then run:

adb devices

List of devices attached
6pt8t8dqzhtwswz5        device
10.5.0.2:58526      device

With that now you can just run your command to run your RN app on the WSA

this is more of a comment, but all this feels very un-intuitive and damn near impossible.

Why do we need to start the metro bundle with --host 127.0.0.1. I can access the bundle fine from windows with a browser without setting the host but its not possible with the emulator that runs in windows. I fail to understand why.

(@luizwhite regarding this comment) for the record, react-native run-android --interactive and react-native run-android --list-devices also call adb -s emulator-5554 emu avd name.

Calling that from Windows returns:

> adb -s emulator-5554 emu avd name
company-tablet
OK

While calling it from WSL returns:

$ adb -s emulator-5554 emu avd name
error: could not connect to TCP port 5554: Connection refused

And if I run it after I call socat, although the packets are captured, my adb session just hangs indefinitely:

$ socat -d -d TCP-LISTEN:5554,reuseaddr,fork TCP:$WSL_HOST:5554
2024/01/03 19:47:27 socat[22203] N listening on AF=2 0.0.0.0:5554
2024/01/03 19:47:33 socat[22203] N accepting connection from AF=2 127.0.0.1:51001 on AF=2 127.0.0.1:5554
2024/01/03 19:47:33 socat[22203] N forked off child process 22205
2024/01/03 19:47:33 socat[22203] N listening on AF=2 0.0.0.0:5554
2024/01/03 19:47:33 socat[22205] N opening connection to AF=2 172.27.208.1:5554
################ Long amount of time passes ################
2024/01/03 19:49:47 socat[22205] E connect(5, AF=2 172.27.208.1:5554, 16): Connection timed out
2024/01/03 19:49:47 socat[22205] N exit(1)
2024/01/03 19:49:47 socat[22203] N childdied(): handling signal 17

I can issue adb devices, adb shell and any other adb commands from my WSL without any issues, it is just this command that is the culprit.

P.S. react-native start and react-native run-android work fine without any issues with socat for port 5037 (ADB server). Linking Windows ADB to WSL ADB helped the other commands to execute fine as well.

@vagnerlandio Genius solution! Thank you. It works well!

@AdalZayas WSA + WSL sounds ideal, but when I try to run

# WSL Terminal
$ adb connect 127.0.0.1:58526 # this is the correct IP:PORT from the WSA Developer Settings area
failed to connect to '127.0.0.1:58526': Connection refused

Any ideas what I may be doing wrong? I've been trying to coax ChatGPT into helping but we've tried about everything including toggling my firewalls. 🙃

For everyone complaining about how insanely, overly-complicated this is, WELCOME TO REACT NATIVE, friends! 🎉 🫠

@corysimmons Try using the ip of your windows machine

@AdalZayas I've tried using every IPv4 that appears in my ipconfig on my Windows machine + that port.

@corysimmons have you tried to turn off all the firewall of wondows, idk why this make a conflict and this block the connection

@AdalZayas Yep. I'm not sure either. I mostly just wanted to confirm you were running adb connect 127.0.0.1:58526 in your WSL Terminal.

@corysimmons Right now im running with my local ip

Added these in my shell rc file

export WSL_HOST_IP="$(tail -1 /etc/resolv.conf | cut -d' ' -f2)"
export ADB_SERVER_SOCKET=tcp:$WSL_HOST_IP:5037
export ADB_TRACE=adb
export EXPO_DEBUG=1
export ANDROID_SERIAL=emulator-5554
export REACT_NATIVE_PACKAGER_HOSTNAME=$(ip addr show eth0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}')

I source it and then after adb deviecs I get

 adb devices                                    
03-04 11:55:52.779 81522 81522 D adb     : adb_trace.cpp:187 Android Debug Bridge version 1.0.41
03-04 11:55:52.779 81522 81522 D adb     : adb_trace.cpp:187 Version 35.0.0-11411520
03-04 11:55:52.779 81522 81522 D adb     : adb_trace.cpp:187 Installed as /home/user/SDKs/Android/platform-tools/adb
03-04 11:55:52.779 81522 81522 D adb     : adb_trace.cpp:187 Running on Linux 5.15.133.1-microsoft-standard-WSL2 (x86_64)
03-04 11:55:52.779 81522 81522 D adb     : adb_trace.cpp:187 
03-04 11:55:52.779 81522 81522 D adb     : commandline.cpp:1646 Using server socket: tcp:172.27.192.1:5037
03-04 11:55:52.779 81522 81522 D adb     : adb_client.cpp:160 _adb_connect: host:version
03-04 11:55:52.780 81522 81522 D adb     : adb_client.cpp:194 _adb_connect: return fd 3
List of devices attached
03-04 11:55:52.781 81522 81522 D adb     : adb_client.cpp:400 adb_query: host:devices
03-04 11:55:52.781 81522 81522 D adb     : adb_client.cpp:358 adb_connect: service: host:devices
03-04 11:55:52.781 81522 81522 D adb     : adb_client.cpp:160 _adb_connect: host:devices
03-04 11:55:52.782 81522 81522 D adb     : adb_client.cpp:194 _adb_connect: return fd 3
03-04 11:55:52.782 81522 81522 D adb     : adb_client.cpp:376 adb_connect: return fd 3
emulator-5554   device

I then proceed launching forwarding

• Disabled windows firewall completely
• In Windows powershell - adb kill-server && adb -a -P 5037 nodaemon server start
• In WSL Ubuntu For port 3037 - socat -d -d TCP-LISTEN:5037,reuseaddr,fork TCP:$(cat /etc/resolv.conf | tail -n1 | cut -d " " -f 2):5037
• In WSL Ubuntu For port 5554 - socat -d -d TCP-LISTEN:5037,reuseaddr,fork TCP:$(cat /etc/resolv.conf | tail -n1 | cut -d " " -f 2):5554

I try yarn android then it crashes

CommandError: Failed to get properties for device (03-04): Command failed: /home/user/SDKs/Android/platform-tools/adb -s 03-04 shell getprop ro.product.cpu.abilist
03-04 12:01:51.982 85678 85678 D adb     : adb_trace.cpp:187 Android Debug Bridge version 1.0.41
03-04 12:01:51.982 85678 85678 D adb     : adb_trace.cpp:187 Version 35.0.0-11411520
03-04 12:01:51.982 85678 85678 D adb     : adb_trace.cpp:187 Installed as /home/user/SDKs/Android/platform-tools/adb
03-04 12:01:51.982 85678 85678 D adb     : adb_trace.cpp:187 Running on Linux 5.15.133.1-microsoft-standard-WSL2 (x86_64)
03-04 12:01:51.982 85678 85678 D adb     : adb_trace.cpp:187 
03-04 12:01:51.982 85678 85678 D adb     : commandline.cpp:1646 Using server socket: tcp:172.27.192.1:5037
03-04 12:01:51.982 85678 85678 D adb     : adb_client.cpp:400 adb_query: host-serial:03-04:features
03-04 12:01:51.982 85678 85678 D adb     : adb_client.cpp:358 adb_connect: service: host-serial:03-04:features
03-04 12:01:51.982 85678 85678 D adb     : adb_client.cpp:160 _adb_connect: host:version
03-04 12:01:51.982 85678 85678 D adb     : adb_client.cpp:194 _adb_connect: return fd 3
03-04 12:01:51.982 85678 85678 D adb     : adb_client.cpp:160 _adb_connect: host-serial:03-04:features
03-04 12:01:51.983 85678 85678 D adb     : adb_client.cpp:372 _adb_connect error: device '03-04' not found
03-04 12:01:51.983 85678 85678 D adb     : adb_client.cpp:376 adb_connect: return fd -1
adb: device '03-04' not found

Any clue ? It looks like parsing/extraction error - but who is responsible for this

1. On native windows adb devices I get

adb devices
List of devices attached
emulator-5554   device

2. On WSL linux adb devices I get

adb devices
03-04 12:29:44.557 16415 16415 D adb     : adb_trace.cpp:187 Android Debug Bridge version 1.0.41
03-04 12:29:44.557 16415 16415 D adb     : adb_trace.cpp:187 Version 35.0.0-11411520
03-04 12:29:44.557 16415 16415 D adb     : adb_trace.cpp:187 Installed as /home/user/SDKs/Android/platform-tools/adb
03-04 12:29:44.557 16415 16415 D adb     : adb_trace.cpp:187 Running on Linux 5.15.133.1-microsoft-standard-WSL2 (x86_64)
03-04 12:29:44.557 16415 16415 D adb     : adb_trace.cpp:187
03-04 12:29:44.557 16415 16415 D adb     : commandline.cpp:1646 Using server socket: tcp:172.27.192.1:5037
03-04 12:29:44.557 16415 16415 D adb     : adb_client.cpp:160 _adb_connect: host:version
03-04 12:29:44.558 16415 16415 D adb     : adb_client.cpp:194 _adb_connect: return fd 3
List of devices attached
03-04 12:29:44.558 16415 16415 D adb     : adb_client.cpp:400 adb_query: host:devices
03-04 12:29:44.558 16415 16415 D adb     : adb_client.cpp:358 adb_connect: service: host:devices
03-04 12:29:44.558 16415 16415 D adb     : adb_client.cpp:160 _adb_connect: host:devices
03-04 12:29:44.558 16415 16415 D adb     : adb_client.cpp:194 _adb_connect: return fd 3
03-04 12:29:44.558 16415 16415 D adb     : adb_client.cpp:376 adb_connect: return fd 3
emulator-5554   device

So there are extra lines coming from a DEBUG flag or something - found it, it is @expo/cli that gets confused

    const splitItems = output.trim().replace(/\n$/, "").split(_os.default.EOL);
    // First line is `"List of devices attached"`, remove it
    // @ts-ignore: todo
    const attachedDevices = splitItems.slice(1, splitItems.length).map((line)=>{
        // unauthorized: ['FA8251A00719', 'unauthorized', 'usb:338690048X', 'transport_id:5']
        // authorized: ['FA8251A00719', 'device', 'usb:336592896X', 'product:walleye', 'model:Pixel_2', 'device:walleye', 'transport_id:4']
        // emulator: ['emulator-5554', 'offline', 'transport_id:1']
        const props = line.split(" ").filter(Boolean);
        const isAuthorized = props[1] !== "unauthorized";
        const type = line.includes("emulator") ? "emulator" : "device";
        return {
            props,
            type,
            isAuthorized
        };
    }).filter(({ props: [pid]  })=>!!pid
    );
```

@vagnerlandio thanks for tips. I think I almost there but Im getting error in the WSA when starting Expo in development build: "Unable to load script.Make sure you are running Metro." and then when i try to reload it loses connection to development server.
Does anybody here make it work with Expo ? Expo Go works on WSA.