If you installed Android Studio from a package but didn't set up your shell, this is likely the case. In the meantime, developers should make sure that the adb binary in your PATH is the one that matches your Android SDK. Instead, I'd suggest throwing an error when ANDROID_HOME isn't set and/or adb isn't found in PATH. IMHO, xdl shouldn't package adb binaries since any revisions to the installed Android SDK will break xdl and its dependents. Usually you get the google-able message that brings us here, but sometimes you'll get an out of date adb that makes Genymotion unhappy. The xdl-spawned adb will attempt to spawn its own daemon, but fail to bind to port 5037.ĭepending on time slicing, 2 and 3 may run out of order.The xdl-spawned adb command will kill the Genymotion-spawned daemon.
In my testing, Genymotion will almost instantly restart the adb daemon when it exits. This will happen for anyone with a poorly configured PATH and modern SDK (which currently ships with adb 1.0.39). killing." is on STDOUT and disappears when run by xdl.
EXPO XDE MAC EMULATOR INSTALL
binaries/osx/adb/adb reverse tcp:5037 tcp:5037Įrror: could not install *smartsocket * listener: Address already in useĪDB server didn 't ACK * failed to start daemon * error: cannot connect to daemon And I am pretty sure you can also modify the usr/local/bin/adb shortcut to point to your platform-tools adb to make things work. Users/myuser/.expo/bin/, copy adb in platform-tools, paste and replace the adb in expo. No terminal command, just use Finder to open /Users/myuser/Library/Android/sdk/platform-tools folder and Instead, I copy the platform-tools adb file to overwrite the expo adb. Adding platform-tool adb path didn't work probably because usr/local/bin is always in the $PATH. So I made the conclusion, expo was using a bad adb. To verify it, I ran /Users/myuser/Library/Android/sdk/platform-tools adb devices, it gave me the ip and port of my virtual android device. I went to /Users/myuser/Library/Android/sdk/platform-tools folder, there was an adb file! This platform-tools adb is apparently what I should use. I have the virtual machine on, but it gave me nothing.
I was pretty sure this expo adb was the criminal all the time. That shortcut points to /Users/myuser/.expo/bin/adb. I went to usr/local/bin and found a shortcut for adb. I typed which adb under the project folder, it showed usr/local/bin/adb. I tried to add export PATH=/Users/myuser/Library/Android/sdk/platform-tools:$PATH and export PATH=/Users/myuser/Library/Android/sdk/tools:$PATH and then source ~/.bash_profile in my project folder. I magically had some other adb in Expo folder, I replaced it with Android SDK adb to remove the last obstacle. I am using Android SDK adb on Android Studio, Expo and Genymotion now. I struggled several hours to make it work.
0 kommentar(er)
