Resolve adb version mismatch and PATH issues #153
Comments
I'm facing the same issue. Any updates on this matter? |
Same issue |
Actually, I just clicked restart project on the XDE (without holding down shift) and restarted the emulator in Genymotion and now it works... |
Same issue |
Same issue. Restarting project + emulator did nothing for me. |
I was able to make it work by setting up Android Studio correctly. |
Same issue |
For anyone reading this, please try this guide: https://docs.expo.io/versions/v17.0.0/guides/genymotion.html If it doesn't work for you, please post the error message and any other information you think may be relevant. Thank you! :) :) |
I followed the instructions, previously I did not have the PATH set in my state file, but now it is there after running:
But I am still getting the error:
|
which of the options did you use from that guide @vstlouis? did you try both? |
@brentvatne I tried both. But what ended up working was
I probably installed the SDK wrong or installing via android studio doesn't play well with Genymotion. |
if you're coming to this issue because you're having the same problem, please follow the instructions at https://docs.expo.io/versions/latest/guides/genymotion.html and then if that doesn't work, try the instructions that @vstlouis provided above. if the problem persists, please explain that you tried all of these things and give us as much information as possible about your environment |
I'm also having this issue. I followed the instructions in the docs and got this error:
I then installed Android SDK by downloading it from Google's website and using the Mac OS X desktop installer. I then pointed Genymotion to that SDK. The same error occurs. I was unable to follow @vstlouis 's approach; the Genymotion works otherwise (the simulator starts up fine); i have a fake Nexus 5. Just no Expo on it ;) |
I am having this issue as well on my macbook |
hmm.. @merges maybe we can do a screenshare sometime? |
I am getting the same problem as vstlouis. Running Ubuntu 16.04. I have a fake Nexus 5X, and Genymotion seems to work otherwise. Edit: i was wrong, vstlouis's solution worked for me. |
Seems like expo adds adb symlink to /usr/local/bin on OSX. I fixed it by pointing to my Android SDK adb:
|
vstlouis's solution worked for me as well. |
I think Option 1 from the docs (https://docs.expo.io/versions/v18.0.0/guides/genymotion.html) does not work for anyone as far as I could read on different threads. A more complete Option 2:
|
I was able to fix this by following @vstlouis' solution, but only after symlinking |
Hey. Does anyone have an idea where are Genymotion tools located on Windows? I've searched my whole profile folder and nothing there. It's not in the install folder either. I would like to avoid installing Android Studio, I don't like to mess up my system more than necessary. |
@mitel 's solution work for me !! (I'm using mac pro) |
@mitel's solution worked perfectly on my mac. Thank you so much! |
I followed @mitel 's steps and I still get this error message on Expo:
I am probably doing something wrong here though because I installed adb via brew, but I am pointing my path to '/mins/Library/Android/sdk' (sdk installed via android studio). I got a message of 'Android SDK tools found successfully'. Pointing it to the path that I got via 'which adb' - /usr/local/bin/adb, led to 'Android SDK not found at this location' Also is there any particular virtual device that we should be using or any virtual device would do? |
I solved the issue by setting the ANDROID_SDK_ROOT env variable in ~/.profile: I've installed the Android SDK tools with brew: |
@mitel's solution and exporting |
I ran into this same error
Following these steps I was able to get it working with Genymotion and Android Studio (found in https://docs.expo.io/versions/v19.0.0/guides/genymotion.html):
|
One thing that i found on Mac, if you do not have adb in the path, Expo will copy adb in a ~/.expo folder and whenever you try to run the android app it will fail with the following error: ADB server didn't ACK After deleting that folder and setting the path to Android SDK installed by Android Studio worked just fine. I'm using GenyMotion. |
cc @fson if you have time to look at this |
I have this issue in ubuntu when trying to start a project created with
|
I solve the problem thanks to the analysis this guy https://stackoverflow.com/a/45456154/6115334, the problem was that I had a old |
|
Don't know exactly but i tried many thing.
Make sure Following things are set:
Below things are not mandatory to follow ..this is just for reference: --and then run android emulator from EXPO and BOOM!! |
@ankit7878 Thank you for sharing! Your solution worked for me after struggling with this issue for quite a while! The only difference is that i didn't install the android SDK separatly but actually used the one included with Genymotion. |
I struggled several hours to make it work. I am using Android SDK adb on Android Studio, Expo and Genymotion now. I magically had some other adb in Expo folder, I replaced it with Android SDK adb to remove the last obstacle. Here is the detailed debugging process. I tried to add I typed I went to So I made the conclusion, expo was using a bad adb. Adding platform-tool adb path didn't work probably because Now everything works. And I am pretty sure you can also modify the |
After setting ANDROID_HOME, PATH variables, app opened on emulator (system Ubuntu, sdk Android studio). |
@diaojinggang Mine works with this way that you tried: |
I had the same problem but have not installed Genymotion and have not installed the SDK via homebrew. I'm just using the SDK installed by Android Studio and the standard emulator. add the following export and paths to your shell config:
Remove the symlink added by xde: Restart your terminal. Then run:
(You will need exp installed Finally restart XDE 😃 |
Thanks @diaojinggang for setting me in the right direction. I too had an adb file that was taking priority in /usr/bin. What I did was simply replace it with the adb file from ~/Android/Sdk/platform-tools and the error is gone. |
If you are using Android Studio instead of Genymotions, like me, I solved it with this cmd: $sudo cp ~/Android/Sdk/platform-tools/adb /usr/bin Thanks for this guy |
tl;dr I think xdl should stop bundling Part of the problem is that xdl silently falls back to an out of date, bundled binary of Currently, [~/OSS/xdl]$ ./binaries/osx/adb/adb reverse tcp:5037 tcp:5037
adb server is out of date. killing...
error: could not install *smartsocket* listener: Address already in use
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon The "adb server is out of date. killing..." is on STDOUT and disappears when run by xdl. This will happen for anyone with a poorly configured PATH and modern SDK (which currently ships with adb 1.0.39). In my testing, Genymotion will almost instantly restart the
Depending on time slicing, 2 and 3 may run out of order. Usually you get the google-able message that brings us here, but sometimes you'll get an out of date IMHO, xdl shouldn't package In the meantime, developers should make sure that the |
Tried about all of these -- make sure you restart XDE for the path changes to take effect |
This is how I solved in Windows 10 |
Following the steps here - https://docs.expo.io/versions/latest/guides/genymotion.html#find-genymotions-copy-of-adb-on-macos worked for me! |
In my case proble was that Genymotion was using it's own sdk. |
After installing Android Studio and GenyMotion under $HOME, I found a
and then the Expo startup began working. I think the socketserver error message must be misleading, as this seems to just be a case of Expo not being able to find the right instance of ADB? |
Thanks @vstlouis your solution works for me: ON LINUX UBUNT 16: 1.-) Removing the android SDK installed by android studio from my path |
I was working on the Linux machine and faced the same issue and after some time found the solution The main reason for this problem is the mismatch of your adb version. Open the terminal and run Now jump into the SDK >> platform-tools and run cd ~/Android/Sdk/platform-tools Simple solution is copy your platform adb to /usr/bin If you are still facing the problem then please visit here |
Closing because this seems to be resolved, I've also just rebuilt the Emulator module to support multiple devices so it's fairly different now. |
Moved from https://github.com/expo/xde/issues/88
The text was updated successfully, but these errors were encountered: