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. Lordgunny

    Dec 14, 2017 10:15

    For me this configuration works fine on Mac:
    Unity version: 2017.2.1f1 ( Maybe works on 2017.2.0f3 too )
    Android Studio: 9.0
    Java SDK: jdk1.8.0_151.jdk ( set the path on Unity preferences after installation )
    Java Tools: tools_r25.2.5 (replace the tools directory after installation of Android Studio )

    This are the relative links download for java
    SDK: http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

    Android Studio: https://developer.android.com/studio/index.html

    Java tools: http://dl-ssl.google.com/android/repository/tools_r25.2.5-macosx.zip

    This are the paths on Unity preferences:
    SDK: /Users/YOUR_USER/Library/Android/sdk
    JDK: /Library/Java/JavaVirtualMachines/jdk1.8.0_151.jdk/Contents/Home

  2. bourriquet

    Dec 12, 2017 09:30

    Not fixed in 2017.2.0f3.

  3. PhoenixEgg

    Dec 09, 2017 19:59

    I have been trying to fix this failing to re-package issue for a day now with no success. Does anyone have a solution for Unity 2017.2.0f3?

  4. redstonegames

    Dec 08, 2017 01:00

    This is not fixed. Still happens in 2017.2.0.p3.

    Unity just cannot be used for any serious development. This is just ridiculous.

  5. as87dgs6asg0a

    Dec 07, 2017 00:10

    This is not fixed. It's happening on my 2017.2

  6. GorillaRoom

    Dec 05, 2017 15:06

    seems in my case its something to do with a legacy scene i started on 5.6 that includes old vuforia elements (pre-unity 2017.2 )

    a blank scene with a cube will build. so Im going to have to start again from scratch adding things one at a time, nooooooooo!

  7. GorillaRoom

    Dec 05, 2017 14:55

    Hi
    Ive come across this problem too,

    Ive tried many variables
    unity 5.6 or 2017.2
    a variety of SDK versions (mainly 26)
    gradle or default builder
    JDK 1.8 or 9
    using that tool_r25 hack or not.

    currently not able to build with
    unity 2017.2
    SDK26
    JDK1.8
    gradle
    and that tools_r25 hack

    any help would be much apprecaited
    cheers
    Tom

  8. algaib

    Nov 25, 2017 15:47

    Finally got it working! Unity 2017.1.2p1, Java SDK 8 (Kit 8u151), Android SDK platform 23 (6.0), replaced the tools folder in the SDK folder with Android SDK tools_r25.2.3.

  9. xxstuartrulesxx

    Nov 18, 2017 21:50

    2017.1.1f1 has the issue?

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.