Search Issue Tracker

Fixed in 2017.1.0f3

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



Found in



Issue ID




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



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
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 "" download and unzip it
5) find MacOSX "" download and unzip it.
6) In the SDK path replace the tools folder.

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

  1. Fdbeb1f205c0c0b6c84cdd584425e0d0?d=mm


    Feb 09, 2018 11:42

    Found a solution:
    1. Follow the workaround above by downloading the 25.2.3 revision of the tools. To find the download link, Google search "" or "" and the link will be the first listed from the website.
    2. Replace the contents of the "tools" folder in that download with the "tools" folder where you Android SDK is located. Tip: I recommend moving the Android SDK to a more accessible location to easily work with it. You can do this in the SDK Manager of Android Studio.
    3. Once this is done, in Unity, under "External Tools", for the Android SDK setting, click Browse and choose the location of the Android SDK folder (this will be one folder up from the "tools" folder that you replaced, not the actual "tools" folder")
    4. Then, close Unity, open it again, and see if it works.
    5. If you then receive an error stating "Cannot determine Java Version from...", then you also need to downgrade your Java JDK. This was my problem as well. I solved it by installing the Java SE Development Kit 8, or as listed on the Java website as: 8u161.
    6. Then, back in Unity, under "External Tools", for the Java setting, click Browse and choose the Java version 8 folder. Unless you renamed it, the folder should be named "jdk1.8.0_161". Unless you set to install it somewhere else, it's path should be: C:/Program Files (x86)/Java/jdk1.8.0_161.
    7. In addition, also ensure that your NDK setting in external tools is set to the "android-ndk-r13b" folder. If you haven't already, you need to download the NDK Revision 13b version by clicking Download next to the setting, and once done clicking Browse and selecting where you installed it.

    Note to Unity: I'd like to say that I am dissapointed that it takes users having to downgrade to older versions of the Android SDK, Java JDK, and Android NDK in order to be able to build any type of Android app directly from Unity. As software developers, we should be more professional than this. I hope that Unity developers are actually working to fix this issue. If not, we should atleast have a guide that states that Unity users deploying to Android should be using these versions. It's as simple as that. Otherwise, your users are scrambling to fix a problem, with real-world deadlines and real-world stresses. Unity developers, you've created a tremendously useful and powerful program, but without understanding your user and his/her problems, you are lessening its usefulness and simply giving people headaches. I urge you to understand our frustration and hopefully act to prevent it.

  2. 39ae4a19e08a53999ec863b35a45ff23?d=mm


    Feb 09, 2018 02:36

    jgwinner, big thank you, worked for me!

  3. 5187cdfc91e14e8d245b55c504d9a82c?d=mm


    Feb 09, 2018 02:17

    This problem still persists in the latest version can we open this issue so we can vote on it? none of the solutions worked for me.

  4. 392c733be260e8124471dce093182d0f?d=mm


    Feb 02, 2018 12:42

    One more thing - if you're tinkering with the Gradle stuff, I recommend making sure that it syncs properly in Android studio, since if it does not - that means that there are some errors and building from Unity will probably not work either. The setup I posted below resulted in my Gradle and Android studio functioning properly with no errors.

  5. 392c733be260e8124471dce093182d0f?d=mm


    Feb 02, 2018 12:37

    For those using Unity 2017.3.0f3 and those still experiencing this issue.

    I found an option which worked for me:

    In android studio, I am using the 4.2.1 Gradle version from

    (this video explains how to upgrade/downgrade Gradle, just plug in the appropriate link where needed

    (Latest version of Gradle is no good, neither did 4.1.something work)

    SDK build tools version (what I could gather from other sources): 25.2.5

    Up until this point I could still not build my app successfully, and the reason was because that I used the latest JDK version (9.0.4). Since Android Studio has its own inbuilt JDK, in Unity I changed the JDK path to Android Studio/jre.

    If that does not work, I suggest downgrading the JDK manually. Hope this helps!

  6. 41da34cde09e59c0d5e8b78418125bd4?d=mm


    Feb 01, 2018 17:06

    Still an issue with 2017.3 and the patches.

  7. 0b7c28845840fe3fdf77001fc22b349f?d=mm


    Feb 01, 2018 16:30

    I am also having the same issue on 2017.3.0f3

  8. 68374e98f3c43615ef06417ea95065f7?d=mm


    Jan 31, 2018 15:31

    Same here on 2017.3!
    Lots of hours lost.

  9. 1e8e9d4cfc279c74192e39e9155746b6?d=mm


    Jan 31, 2018 05:19

    I also have this problem while building for Android.

  10. D7eb86095fbbe96a1684f431fdc4faf6?d=mm


    Jan 29, 2018 04:51

    This bug has regressed and needs to be reopened. Repros in 2017.3.0.f3

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.