Search Issue Tracker

Fixed in Unity 2017.1



Found in


Issue ID




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




Priority: 3Not yet prioritized for a release


Severity: 2No workaround

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

  1. 1c49288d112cd7e903a10e81a69c78db?d=mm


    May 24, 2017 14:45

    This issue should be fixed in:
    5.4.5p2 and higher
    5.5.3p3 and higher
    5.6.0p3 and higher
    and 2017.1 beta 5 and higher

  2. 7cbd817418ce468b875b90077e86ad66?d=mm


    May 22, 2017 04:00

    I can't find the "" file . All i found was "".
    Please help me, I don't know what to do, my unity is up to date but gives me the error "Unable to list target platforms".

  3. 0d50ffc5b14c51659dd9978857ec05fe?d=mm


    May 14, 2017 15:58

    It is FIXED in 5.6.0p4 !!!

  4. 0d50ffc5b14c51659dd9978857ec05fe?d=mm


    May 14, 2017 15:03

    I have 5.6.0p3 but still have this error. I also downloaded latest "Android SDK Tools" 26.0.2 and restart everything but still have "Error:Invalid command manifmerger". I see no other choices than try with the 2017.1.0b3 ...

  5. F9806e9e40149354e1b49cca31df707e?d=mm


    May 12, 2017 15:20

    The merge issue is a weird one and I found that it was to do with the way Unity is creating the manifest file in the temp folder.

    Try adding this default androidManifest.xml to your project under plugins/Android remembering to change the package name and remove any unwanted permissions. The issue seems to come from there being no manifest file to actually merge with and also (when you do add the manifest) there may then be issues with some manifest files in your project (in the other libs and plugins) using incorrect icon references.

    <?xml version="1.0" encoding="UTF-8"?>
    <manifest xmlns:android=""
    <supports-screens android:smallScreens="true" android:normalScreens="true" android:largeScreens="true" android:xlargeScreens="true" android:anyDensity="true" />
    <uses-feature android:glEsVersion="0x00020000" />
    <uses-sdk android:minSdkVersion="19" android:targetSdkVersion="25" />
    <application android:icon="@drawable/app_icon">
    <activity android:name="com.unity3d.player.UnityPlayerActivity" android:label="@string/app_name" android:configChanges="fontScale|keyboard|keyboardHidden|locale|mnc|mcc|navigation|orientation|screenLayout|screenSize|smallestScreenSize|uiMode|touchscreen" android:launchMode="singleTask" android:screenOrientation="landscape">
    <meta-data android:name="unityplayer.ForwardNativeEventsToDalvik" android:value="true" />
    <action android:name="android.intent.action.MAIN" />
    <category android:name="android.intent.category.LAUNCHER" />
    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.VIBRATE" />
    <uses-permission android:name="android.permission.GET_TASKS" />
    <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
    <uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
    <uses-permission android:name="" />

  6. Df1a22687df368a376272c76a32c4703?d=mm


    May 11, 2017 16:24

    Hello everyone,

    The issue has been fixed and the issue tracker above has been updated as to not cause confusion.

    However, with the newest SDK/Build tools we have another issue - Merging manifest files.

    We patched it up a bit in 5.6.0p4, but building Android Oculus is still a no go : (
    We are working on it : )

  7. Ab175e816c63dbf606e5c3c6afa14410?d=mm


    May 11, 2017 03:58

    yeah gee thanks unity devs, did you even test the fix before releasing it? I'm starting to think I should ask for a refund for my pro license, I've just spent a whole week working through unity bugs because you guys don't seem to give a toss anymore

  8. E99da8445aba4449360f7d4a10121afc?d=mm


    May 10, 2017 18:03

    I still have the same problem in the latest version of Unity 5.6.0f3 (on windows 10).

    This issue is fixed in 2017.1, but what version of Unity is that?
    I'm sorry if I don't understand what "Fixed in Unity 2017.1" means, but I guess it means that this issue is fixed in Unity version 2017.1.
    But there is no version of Unity called 2017.1, or am I all wrong here?

    This is the only version of Unity I can find:

    Anyway, I got the problem (and still have) after updating Android Studio to the latest version 2.3.1, which include the latest version of Android SDK.

  9. A2a68be80657a4c47efafadd12817d7c?d=mm


    May 10, 2017 03:59

    In case it helps anyone, I've managed to build around this Manifest error by doing this:

    1) after a failed building attempt, go to the Temp/StagingArea folder in your Unity project, grab the AndroidManifest-main.xml file

    2) copy it into Assets/Plugins/Android, rename it to AndroidManifest.xml

    3) in the file itself, remove "android:theme="@style/UnityThemeSelector" and "android:debuggable="true""

    With that, at least I'm able to build for Gear VR.

  10. A2a68be80657a4c47efafadd12817d7c?d=mm


    May 10, 2017 03:31

    This is the error I get when building for Gear VR (5.6.0p4):

    D:\My-Game\Temp\StagingArea\AndroidManifest-main.xml:4:125-150 Error:
    Attribute application@debuggable value=(true) from AndroidManifest-main.xml:4:125-150
    is also present at AndroidManifest.xml:3:148-174 value=(false).
    Suggestion: add 'tools:replace="android:debuggable"' to <application> element at AndroidManifest-main.xml:4:3-12:17 to override.
    D:\My-Game\Temp\StagingArea\AndroidManifest-main.xml:4:16-57 Error:
    Attribute application@theme value=(@style/UnityThemeSelector) from AndroidManifest-main.xml:4:16-57
    is also present at AndroidManifest.xml:3:83-147 value=(@android:style/Theme.Black.NoTitleBar.Fullscreen).
    Suggestion: add 'tools:replace="android:theme"' to <application> element at AndroidManifest-main.xml:4:3-12:17 to override.


All about bugs

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