Search Issue Tracker

Fixed in 2017.1.0f3

Fixed in 5.4, 5.5, 5.6

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 (133)

  1. 3e2ae4101faf1b19afa71b4540d5dac6?d=mm

    MrDude

    Mar 21, 2017 15:23

    I notice it says "windows.zip" at the end there. Does this imply that the files won't work in OSX? What is the fix for us Mac users?

  2. 2df84f092fc9513a81f59210dc72a036?d=mm

    jr_mike

    Mar 16, 2017 22:34

    @JGWINNER : That fix does indeed work, thanks for providing that. Only problem is you can build an APK but you cannot 'Build and Run' to deploy to the device through Unity after doing that, since it doesn't seem to work with ADB correctly.

    I'm pretty sure this is some really, really old pre-gradle era Unity code that checks to see if ANT is available, but because it's removed from the Android SDK now, it assumes the SDK isn't installed.

  3. 589b000609d09d1d27f02554af06d1f0?d=mm

    jgwinner

    Mar 09, 2017 08:48

    Thanks Leva - right, I found the fix:

    Upgrading to the latest does not work; that's what caused my problem :) They removed a feature and called it "Deprecated" without any warnings (this is not deprecation, it's removal).

    The fix is to rename the "Tools" directory in the Android SDK.

    Go to Unity, got to Edit->Preferences, then "External Tools"

    Note where the Android SDK is located.

    Go there, and rename the "Tools" folder to Tools-XXXX (replace XXX with version).

    Then, download this file:

    http://dl-ssl.google.com/android/repository/tools_r25.2.5-windows.zip

    Unzip it to the "Android SDK" location you found in the first step. Make sure it's "Tools".

    Then, exit and reload Unity - build. It should work.

    Credit to this thread on stack overflow: http://stackoverflow.com/questions/42538433/not-finding-android-sdk-unity and https://code.google.com/p/android/issues/detail?id=235455#makechanges

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.