Search Issue Tracker

Fixed in 2017.1.0f3

Fixed in 5.4, 5.5, 5.6

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

  1. A2a68be80657a4c47efafadd12817d7c?d=mm

    jazzpablo

    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.

    UnityEditor.HostView:OnGUI()

  2. A2a68be80657a4c47efafadd12817d7c?d=mm

    jazzpablo

    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)

  3. F0bb3db6ee0d8462d6701b6b3bcb60c0?d=mm

    ikerion

    May 09, 2017 08:32

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

  4. A2a68be80657a4c47efafadd12817d7c?d=mm

    jazzpablo

    May 09, 2017 02:16

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

  5. Be0e12e6206c15f052b6f9924768d419?d=mm

    Bruno-Meneghetti

    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!

  6. A2a68be80657a4c47efafadd12817d7c?d=mm

    jazzpablo

    May 06, 2017 10:03

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

  7. 23d1c27a10aaeed222250ef169d3090b?d=mm

    f413dm-matthews454460

    May 06, 2017 00:27

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

  8. 29613556152cd8ccd6dc98a90dc8be5a?d=mm

    pixellabs

    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?

  9. E2034f7753b52d221306edf828d6353e?d=mm

    Adam-VisualVocal

    May 03, 2017 19:15

    Re: Unity 5.6.0p3 does NOT fix this issue
    I totally agree with ObsidianX. I just lost a day fighting the "Error:Invalid command manifmerger" issue until I found this thread.

  10. Df1a22687df368a376272c76a32c4703?d=mm

    Evaldas_Unity

    May 03, 2017 13:28

    Hey everyone!
    Sorry that the tag at the top says that it is fixed in 2017.1. That's just how our system marks fixed versions.
    To be precise this issue should be fixed in 2017.1.0b3, 5.5.3p3, 5.4.5p2 when those come out, and is fixed in 5.6.0p3.

    Hope this brings some clarity : )

    Evaldas
    Unity QA

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.