Search Issue Tracker

Fixed in 2017.1.0f3

Fixed in 5.4.X, 5.5.X, 5.6.X

Votes

39

Found in

5.5.2f1

2017.2.0f3

Issue ID

888859

Regression

Yes

Android Build fails when the latest Android SDK Tools 25.3.1 version is used

Android

-

How to reproduce:
1. Update Android SDK Tools to 25.3.1
- In Mac open Android Studio -> Check for updates and update Android Studio version (might be not necessary)
- In Android Studio -> Preferences -> Appearance & Behavior -> System Settings -> Android SDK -> SDK Tools
2. Create a new Unity project
3. Build and run on Android device
Result: Build fails "CommandInvokationFailure: Unable to list target platforms. Please make sure the android sdk path is correct. See the Console for more details. ..."

Reproducible: 5.5.2p2, 5.6.0b11, 2017.1.0a3

Note: I haven't been able to reproduce this issue on Windows machine. As after update via Android Studio, SDK Manager still doesn't see SDK Tools 25.3.1 version and uses 25.2.5

Workaround for the customers.

1) just open https://developer.android.com/studio/index.html
2) scroll down to the bottom of that page
3) go to downloads
4) scroll down to the bottom of that page
5) find Windows "tools_r25.2.3-windows.zip" download and unzip it
5) find MacOSX "tools_r25.2.3-macosx.zip" download and unzip it.
6) In the SDK path replace the tools folder.

FIXED:
Unity versions: 5.4.5p2, 5.5.3p3, 5.6.0p3, 2017.1.0b3
SDK Tools have to be updated to 26.x.x

Comments (172)

  1. deepinderpanesar

    Aug 23, 2022 10:50

    Please try 24th version SDK, Because 24th is unstable

  2. haichtop

    Sep 19, 2021 12:33

    ok good very best as compare to other

  3. hkb88

    Dec 28, 2020 14:03

    ok good

  4. nikita323

    Dec 26, 2020 21:38

    ok

  5. samehfr

    Sep 07, 2020 15:06

    Reproduced on Windows 10
    Unity 5.5.1f1 Personal
    Android Studio 2.3
    Android SDK Tools 25.2.5

  6. samehfr

    Aug 31, 2020 21:47

    good job

    thank and thanks

  7. samehfr

    Aug 18, 2020 07:28

    thanks good site

  8. Duobix

    Apr 05, 2019 11:09

    Ok, the workaround didn't work. had to go to my sdk folder, and from there delete the whole build-tools folder - that made Unity 2018.3.10f1 finally able to build without the SDK error.

  9. Duobix

    Apr 05, 2019 10:36

    Issue still present on Unity 2018.3.10f1 + OSX 10.14, had to use the workaround provided in the issue description.

  10. KReguieg

    Dec 04, 2018 14:09

    Still not working in 2018.2.3f1!!! Had to do the workaround again...

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.