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

  1. porandojin1

    Jan 18, 2018 13:21

    still an issue. almost for a year now.

  2. DemonGamesStudio

    Jan 10, 2018 13:19

    Still an issue for me. I tried the new tools i tried the old tools. Been stuck for days. Going to make a new post, since for some reason this is marked as resolved.

  3. hilllo

    Jan 10, 2018 00:24

    Agree with @ALCATRAZZGAMES the problem is still here.

    fix here works for me as well: (watch from 50s)

  4. AlCaTrAzzGames

    Jan 08, 2018 03:49

    can confirm this bug still exists in 2017.3.0f3, if you install the latest version of android studio

    fix here works: (watch from 50s)

  5. daraOke

    Jan 05, 2018 02:54

    I am getting a different error. The one where ':prepareUnityAdsLibrary' as a task already exists. Could not find a fix anywhere. Any ideas, please?

  6. OneLemon

    Jan 04, 2018 20:04

    Ok, what I found out is, if anyone is using any android plugins (In my case, stan's assets native android plugin), it may create's this error and/or the "unable to merge androidmanifest.xml" one.

    After trying different android SDKs and JDKs and it still doesn't work, try removing any android plugins and see if you still get this error. It worked for me.

    Good luck.

  7. OneLemon

    Jan 04, 2018 15:51

    This is broken again in 2017.3.0f3, was working fine in my previous verison of Unity 5.6.3

    Win10 x64

    -JDK 1.8.0_152
    -JDK 1.8.0_131

    Nothing is working, fix this, it's not acceptable.

  8. BloodyBeard

    Jan 02, 2018 10:15

    Still broken with 2017.2.0p2 and 2017.2.0f3
    win10(64bit), SDK platform tools 27.0.1 SDK tools 26.1.1, JDK 9.0.1

    Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema
    Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(Unknown Source)
    at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(Unknown Source)
    at java.base/java.lang.ClassLoader.loadClass(Unknown Source)
    ... 5 more


  9. bencuska

    Dec 30, 2017 00:38

    I got mine working with Unity 3.0.0f3 (64bit) , current sdk with android studio, the sdk hack the op wrote and i had to downgrade my jdk to 1.8.0_152 . Hope this helps (I've been struggling with this for a week now)

  10. gdwf

    Dec 29, 2017 16:18

    Broken in 2017.3.0f3 (win64)

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.