Search Issue Tracker

Fixed in 2017.1.0f3

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

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
Log in to vote on this issue

Comments (172)

  1. CGVMLG

    Sep 24, 2017 18:37

    Still in 5.6.3p2 and using java jdk 9

  2. walterg77

    Sep 06, 2017 08:06

    This is still an issue in 2017.1.1f1.

    I'm trying to build the Oculus Unity Utilities and the only way that I've been able to build an apk was to use the tools_r25.2.3-windows.zip file.

  3. krisventure

    Aug 27, 2017 20:19

    Yes, definitely still present in the latest Unity, just updated to 2017.1.0f3 and had the same issue. Only difference my error message when trying to build just an empty project (with android a VR supported) is "Unable to merge android manifests". The same workaround fixed it. The same workaround also fixed an unwanted READ_PHONE_STATE permission automatically added with no reason. replacing the android tool folder now removed this otherwise unremovable permission that warned user that my app "wants to make phone calls" or something silly like that.

  4. Graybull

    Aug 07, 2017 21:24

    I believe I have found a resolution to this for the mean time. Look through your {Project-Dir}/Temp/StagingArea/android-libraries and see if any of the plugins contain an AndroidManifest.xml with an <application> tag containing conflicting attributes. The problem seems to lie in the {Assets}/Plugins/UnityPurchasing/Bin/Android, the plugins contain application attributes that'll conflict with the master AndroidManifest. At the moment, I'm able to build without issue after deleting the {Assets}/Plugins/UnityPurchasing/Bin/Android folder. But, this creates another issue with not having IAP working with google play. Hope this gets resolved soon.

  5. DessIntress

    Aug 04, 2017 18:00

    Same problem with the current version 2017.1.0f3 and the android sdk 26

  6. haha2014

    Aug 01, 2017 18:58

    I upgraded to sdk tools to 26.0.2 and got another problem that unity cannot merge manifest.
    I fixed this problem by replacing the "tools" folder with tools_r25.2.3 (Studio > tools)

    Mac: https://dl.google.com/android/repository/tools_r25.2.3-macosx.zip?hl=id
    Windows: https://dl.google.com/android/repository/tools_r25.2.3-windows.zip?hl=id

  7. iko-

    Jul 31, 2017 13:36

    I've found the error on Unity 2017.1.0f3. It's solved by the previous workaround.

  8. otyx

    Jul 31, 2017 08:34

    This problem is not closed! This issue is still happening: hardcodeddebug mode is still breaking the apk build.

    I have tried with a new clean project on Unity 2017.1.0f3 on MacOSX and Windows 10. There are no AndroidManifest files in the project but when one is generated, android:debuggable="false" is being inserted. This cannot be overridden with a custom AndroidManifest in /plugins/Android.

    I have tried including the tools xmlns and using tools:replace="android:debuggable" as well as tools:remove="android:debuggable" in the application tag of the androidmanifest but the debuggable="false" is STILL being inserted into the same tag and generating an error.

    Unity 2017.1.0f3, Gradle build, IL2CPP

    Could someone please take a look? The above fixes and tool versions are not working for me.

  9. hMark

    Jul 28, 2017 07:36

    I wrote an article about proper installation:
    http://devlog.markhlavac.com/2017/06/30/installing-android-sdk-for-unity3d-using-sdk-tools-and-cli/

  10. tricalnikhil

    Jul 25, 2017 23:18

    The Downloads url might have changed to https://dl.google.com/android/repository/tools_r25.2.3-macosx.zip?hl=id
    or, for the latest - https://dl.google.com/android/repository/tools_r25.2.5-macosx.zip?hl=id

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.

Latest issues

See all new issues