You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 18, 2024. It is now read-only.
I am developing on Windows 11 using the Windows Subsystem for Linux (WSL). I have now the challenge that I am running my Expo app through Ubuntu/WSL but I also have to loop my Android device connection from Windows to the WSL. Thankfully there was this guide that showed me how to host an adb server on Windows and how to connect to it from Ubuntu.
Hosting it on Windows:
adb -a -P 5037 nodaemon server
Running adb devices on Ubuntu:
adb -H 172.20.16.1 -P 5037 devices
When I try to run now expo run:android, I am getting the following error:
CommandError: No Android connected device found, and no emulators could be started automatically.
My guess is that Expo calls adb without the -H 172.20.16.1 -P 5037 flags. Is there an option / env config to set these flags?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am developing on Windows 11 using the Windows Subsystem for Linux (WSL). I have now the challenge that I am running my Expo app through Ubuntu/WSL but I also have to loop my Android device connection from Windows to the WSL. Thankfully there was this guide that showed me how to host an adb server on Windows and how to connect to it from Ubuntu.
Hosting it on Windows:
Running
adb devices
on Ubuntu:When I try to run now
expo run:android
, I am getting the following error:My guess is that Expo calls
adb
without the-H 172.20.16.1 -P 5037
flags. Is there an option / env config to set these flags?Beta Was this translation helpful? Give feedback.
All reactions