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
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
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Scene View] Gizmos dropdown disappears while toggling Windzone checkbox with its tooltip open
- Crash in StackAllocator::TryDeallocate when calling ParticleSystemRenderer.BakeMesh
- Modifying scoped registries in project manifest does not update Package Manager UI window
- Models change their position in scene when upgrading project
- Texture 'Read/Write' option does not double the memory in Profiler
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.
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?
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.
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
ObsidianX
May 03, 2017 01:04
Unity 5.6.0p3 does NOT fix this issue. The build still fails but this time at the "Merging Manifests" step with the following error:
CommandInvokationFailure: Unable to merge android manifests. See the Console for more details.
/Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/bin/java -Xmx2048M -Dcom.android.sdkmanager.toolsdir="/Users/me/android-sdk/tools" -Dfile.encoding=UTF8 -jar "/Applications/Unity 5.6.0p3/PlaybackEngines/AndroidPlayer/Tools/sdktools.jar" -
stderr[
Error:Invalid command manifmerger
]
stdout[
]
exit code: 64
UnityEditor.Android.Command.Run (System.Diagnostics.ProcessStartInfo psi, UnityEditor.Android.WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg)
UnityEditor.Android.AndroidSDKTools.RunCommandInternal (System.String javaExe, System.String sdkToolsDir, System.String[] sdkToolCommand, Int32 memoryMB, System.String workingdir, UnityEditor.Android.WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg)
UnityEditor.Android.AndroidSDKTools.RunCommandSafe (System.String javaExe, System.String sdkToolsDir, System.String[] sdkToolCommand, Int32 memoryMB, System.String workingdir, UnityEditor.Android.WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg)
UnityEditor.BuildPlayerWindow:BuildPlayerAndRun()
zakirshikhli
Apr 25, 2017 17:21
Same issue with 26.0.1 Workaround is to: Downgrade to 25.2.5, then export to Android Studio, Update to 26.0.1, then build. Export is necessary because on 25.2.5 SDK, game does not launch.
Reason is missing "internet permission" on Manifest. It has to be added manually via Android Studio
wassim-s-haddar
Apr 22, 2017 18:54
Thanks a lot that really helps out in Unity 5.6.0f3
ethanwgross
Apr 21, 2017 22:29
@MRDUDE you rock dude. only working link for that file I could find anywhere.
carocky
Apr 21, 2017 11:59
Thanks JGWinner for linking the old tools. I have just built a new PC and installed unity/android from scratch. Can't find the old tools anywhere - except from your link!
Studiomaurer
Apr 07, 2017 15:27
For me the fix isn't woking, it seems to want 26.0.0 explicitly.
* What went wrong:
A problem occurred configuring root project 'gradleOut'.
> failed to find Build Tools revision 26.0.0
Hmm, what now?