Update Android emulator path to support SDK Tools >=25.3.0 #700
Conversation
Since Android SDK Tools 25.3.0 (March 2017) The Android Emulator was removed from the SDK Tools package and moved to a different SDK directory. For recent API versions (and depending on the OS architecture) running the old tools/emulator can cause errors because the different architecture versions of the emulator won't be found in the tools folder of the Android SDK. Given that from August this year the minimum target version required for submitting apps to the Play store will be API 26, the path of the emulator should be updated.
|
I think it would be better to support both paths in order of preference than just drastically switch to another location. Anyway your observation is very nice. To my embarrassment, I also had this problem, but didn’t figure out the reason behind it, so I’ve been fiddling with folders and files in my SDK till it worked. Now I know, thanks! |
Updated the constructor to use the new Emulator path if it exists, or else continue using the old emulator path. This allows backward compatibility with users of older Android SDK versions.
|
@noomorph you're right. I've updated the pull request to check first if the new emulator path exists before using it, and otherwise falling back to the previous path. |
|
@rotemmiz , actually this is a useful pull request 👍 . Today I was lazy to get AVD with API 26 on the other MacBook, so I tried to run the project on Nexus API 27 and only with the change in PR it works. What do you think? Maybe we can fix a couple of things in PR if there's something you don't like and merge? Why not? |
|
Sure! Lets do it! |
rotemmiz
changed the title
Since Android SDK Tools 25.3.0 (March 2017) The Android Emulator was removed from the SDK Tools package and moved to a different SDK directory: Android Emulator v15.3.0 release notes
Also, according to this issue in the google issue tracker the new path is also the preferred way of invoking the emulator, and the old path will at some point be deprecated / removed.
For recent API versions (and depending on the OS architecture) running the old tools/emulator can cause errors because the different architecture versions of the emulator won't be found in the tools folder of the Android SDK. By example, I'm using the Android SDK v27 build tools and the latest versions of all the Android tools, and when running the emulator with the command that detox uses I get the following errors:
Given that from August this year the minimum target version required for submitting apps to the Play store will be API 26, the path of the emulator should be updated.