Search Issue Tracker

Fixed in 2017.1.0f3

Fixed in 5.4, 5.5, 5.6



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

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

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


  4. A2a68be80657a4c47efafadd12817d7c?d=mm


    May 10, 2017 03:18

    Actually I'm still getting this error when building for Gear VR (I don't get it anymore when building for Cardboard)

  5. F0bb3db6ee0d8462d6701b6b3bcb60c0?d=mm


    May 09, 2017 08:32

    Using 5.6.p04, still getting the "Unable to Merge Android manifest"

  6. A2a68be80657a4c47efafadd12817d7c?d=mm


    May 09, 2017 02:16

    It's working well for me now in 5.6.p04.

  7. Be0e12e6206c15f052b6f9924768d419?d=mm


    May 08, 2017 15:43

    The problem with merging the Manifests as stated by OBSIDIANX is supposedly fixed on the new patch 5.6.0p4 released today (may 08). I'll try it now!

  8. A2a68be80657a4c47efafadd12817d7c?d=mm


    May 06, 2017 10:03

    Using 5.6.p03 I'm also getting the error message "Error:Invalid command manifmerger"..

  9. 23d1c27a10aaeed222250ef169d3090b?d=mm


    May 06, 2017 00:27

    I started fresh with the advised "", in Unity 5.6.0p3, and I am receiving this error. This issue is not resolved.

  10. 29613556152cd8ccd6dc98a90dc8be5a?d=mm


    May 05, 2017 13:24

    So is there any solution/workaround to "Error:Invalid command manifmerger", or do we have to wait for another Unity patch?

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.