Fixed
Status Update
No update yet.
Comments
ky...@gmail.com
Facing same problem here. Not sure why 'android' command no longer working.
ky...@gmail.com
I rollbacked to old Android SDK and Unity can build the project again.
ko...@gmail.com
[Comment deleted]
ak...@gmail.com
Got the same issue, answer is given in the following thread.....
http://stackoverflow.com/questions/42538433/not-finding-android-sdk-unity#
mine solved perfectly, also don't forget to copy zip align from one of the build tools(Android/sdk/buildtools) to the tools(Android/sdk/tools) folder, though newer versions might work without it, but still...!
hope this helps..!!
mine solved perfectly, also don't forget to copy zip align from one of the build tools(Android/sdk/buildtools) to the tools(Android/sdk/tools) folder, though newer versions might work without it, but still...!
hope this helps..!!
ea...@google.com
The older android sdk command is deprecated, and replaced with sdkmanager ( https://developer.android.com/studio/command-line/sdkmanager.html ). The sdkmanager command line tool is shipped inside of Android SDK Tools as of Nov 2016 (https://developer.android.com/studio/releases/sdk-tools.html )
You can download the latest version of the stand-alone sdkmanager command line tool from the Android Studio download page:https://developer.android.com/studio/index.html (go to the very bottom of the page)
You can download the latest version of the stand-alone sdkmanager command line tool from the Android Studio download page:
ob...@gmail.com
I understand that "sdkmanager" is the new tool (and is much simpler for SDK management, so thank you!) but older versions of Unity won't receive updates to learn about this new tool. Completely dropping support for it is breaking Unity at least up to version 5.5.0. Deprecation typically means including an additional nag that says to stop using a particular feature, not deleting it without warning and breaking other toolchains entirely.
I was able to copy the "android" script and all the dependencies from the old tools version 25.2.3 into the current version without a problem but this is not sustainable.
The expectation here is that SDK updates do not break backwards compatibility with existing build systems, especially one as heavily used as Unity3D.
I was able to copy the "android" script and all the dependencies from the old tools version 25.2.3 into the current version without a problem but this is not sustainable.
The expectation here is that SDK updates do not break backwards compatibility with existing build systems, especially one as heavily used as Unity3D.
je...@gmail.com
+1 on @obsidianx's comment
Note that Unity isn't the only one affected. Seehttps://github.com/cocos2d/cocos2d-x/issues/17424 as example
My experience was the following: I fired Android Studio yesterday on my developer machine. It proposed to update itself and doing so, updated the SDK and broke my Unity/Android build setup. I won't be able to upgrade Unity on many projects, and the versions we use will not receive updates to make it compatible with newer versions of the Android SDK.
Keeping more backward compatibility would be better for the whole ecosystem. If not possible, the user should be aware of the removed backward compatibility before upgrading.
Note that Unity isn't the only one affected. See
My experience was the following: I fired Android Studio yesterday on my developer machine. It proposed to update itself and doing so, updated the SDK and broke my Unity/Android build setup. I won't be able to upgrade Unity on many projects, and the versions we use will not receive updates to make it compatible with newer versions of the Android SDK.
Keeping more backward compatibility would be better for the whole ecosystem. If not possible, the user should be aware of the removed backward compatibility before upgrading.
jo...@gmail.com
Another unity user here. Can't believe that this tool got deleted, not just marked as deprecated without any obvious advance warning, and with no workaround script put in while people get used to the tool being missing.
jo...@gmail.com
Agreed - "Deprecated" doesn't mean "Removed". If you say "Was Deprecated" when something breaks, that meant "Was Deprecated in a previous version".
Whoever decided to just flat remove it, should learn something about large distributed projects that are used in countless other projects - they turn about as easy as the Queen Mary.
I can confirm in my case it fixed my Unity problem. Haven't tried the Studio yet, will do shortly.
== John ==
Whoever decided to just flat remove it, should learn something about large distributed projects that are used in countless other projects - they turn about as easy as the Queen Mary.
I can confirm in my case it fixed my Unity problem. Haven't tried the Studio yet, will do shortly.
== John ==
[Deleted User] <[Deleted User]>
[Comment deleted]
[Deleted User] <[Deleted User]>
Apparently it also breaks cordova/Ionic framework.
What does help is
- taking android script from old sdk.
- taking all files from tools/lib that are not present in most recent release
- taking all files from templates dir
and putting them in to the new sdk.
What does help is
- taking android script from old sdk.
- taking all files from tools/lib that are not present in most recent release
- taking all files from templates dir
and putting them in to the new sdk.
ja...@gmail.com
We have this problem aswell.
ea...@google.com
ha...@gmail.com
[Comment deleted]
ma...@hotmail.com
"Yay! let's just remove the 'android' command line tool :D what could possibly go wrong?!
You morons.
You morons.
sa...@ehealthnigeria.org
[Comment deleted]
gn...@gmail.com
Downgrading the whole SDK tools version to 25.2.3 worked for me
Links available here
http://stackoverflow.com/a/42552342/254823
Links available here
et...@gmail.com
Rollback my SDK tools was not an option, since like many I want to be able to use Unity without impacting my day-to-day Android development environment.
The solution for this is to make a separate android SDK setup for Unity.
Download tools in your desired Unity-specific-android SDK folder, unzip the tools 25.2.3 in it.
Go to Unity's preferences, point to this specific folder, Unity will download the dependencies it needs.
I think the 'fix' for this would be for 3rd party platforms layering on top of the Android build system to follow along. But hopefully someone at Google could ping their partners, since this right now makes Daydream and Tango Unity integrations rather broken.
The solution for this is to make a separate android SDK setup for Unity.
Download tools in your desired Unity-specific-android SDK folder, unzip the tools 25.2.3 in it.
Go to Unity's preferences, point to this specific folder, Unity will download the dependencies it needs.
I think the 'fix' for this would be for 3rd party platforms layering on top of the Android build system to follow along. But hopefully someone at Google could ping their partners, since this right now makes Daydream and Tango Unity integrations rather broken.
ex...@gmail.com
Same problem. Please do not break compatibility with old projects. Not everyone likes Android Studio!
ke...@google.com
Same problem.
I just start running Daydream/Tango codelab last week, latest Unity + latest Android SDK would reproduce this error. Replacing the android sdk/tools directory with old version (25.2.3) fixed it.
Please fix the problem, as now it's kind of magic as old version of android sdk tools_r25.2.3-macosx.zip is not on download page any more, I found the url to download in herehttps://issuetracker.unity3d.com/issues/android-build-fails-when-the-latest-android-sdk-tools-25-dot-3-1-version-is-used
Regards
I just start running Daydream/Tango codelab last week, latest Unity + latest Android SDK would reproduce this error. Replacing the android sdk/tools directory with old version (25.2.3) fixed it.
Please fix the problem, as now it's kind of magic as old version of android sdk tools_r25.2.3-macosx.zip is not on download page any more, I found the url to download in here
Regards
ob...@gmail.com
Despite Google's speedy attempt at fixing the situation, it turns out my initial report wasn't entirely correct. Unity does use the "android" tool set from the older versions of the SDK but does so by loading the JAR files directly, not calling the "android" command like it appears from the logs. You can fix the build by copying over the old sdkmanager.jar (and dependencies) to your tools/ folder for a quick fix. While I think it would be wonderful for Google to bring the JAR back to fix the build from their end I believe that Unity developed a bad build system by relying on internals of the Android SDK instead of utilizing the public interfaces.
yu...@unity3d.com
#21 this is correct, Unity is using the jars and not the script itself.
Using latest Android SDK Tools (26.0.1 IIRC) and latest Unity patch releases should work. However without updating to latest patch release in the Unity major version you're using it won't work.
Using latest Android SDK Tools (26.0.1 IIRC) and latest Unity patch releases should work. However without updating to latest patch release in the Unity major version you're using it won't work.
ks...@google.com
For affected Unity folks, could you let us know if you're on an older version that's not getting the patch release versus if you are covered by it?
ma...@hotmail.com
Excuse me google folks but WHAT THE FUCK ARE WE TALKING ABOUT? There's no "which version you are using?", "on my machine using this patch it works" etc. IMMEDIATELY PUT THAT FUCKING 'android' COMMAND LINE SHIT BACK IN YOUR PITFUL SDK. This is all you need to know and there's no more time to be wasted in pointless argumentations.
je...@gmail.com
ks...@google.com: We are not able to upgrade to latest version of Unity all the time for various reasons. I have some old projects on Unity 4.7.1, others on 5.3.6, others on 5.6.
We are upgrading the old ones as fast as we can :)
We are upgrading the old ones as fast as we can :)
jb...@google.com
According to J, Kevin is working on this with Unity.
jb...@google.com
kk...@google.com
Two action items:
1) Talk to Unity to backport the SDK tools
2) Talk to DevRel to set up a page where users can download
1) Talk to Unity to backport the SDK tools
2) Talk to DevRel to set up a page where users can download
jo...@google.com
Thanks for the feedback and sorry for the delay. We believe this has been fixed in later versions. Please reopen if you see this behavior again. Thanks.
Description
Unity3D build log:
Error building Player: CommandInvokationFailure: Unable to list target platforms. Please make sure the android sdk path is correct. See the Console for more details.
/Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/bin/java -Xmx2048M -Dcom.android.sdkmanager.toolsdir="$HOME/Library/Android/sdk/tools" -Dfile.encod
ing=UTF8 -jar "/Applications/Unity 5.5.0f3/PlaybackEngines/AndroidPlayer/Tools/sdktools.jar" -
stderr[
Error:Invalid command android
]
stdout[
]
exit code: 64
(Filename: Line: -1)
$ android
The android command is no longer available.
For manual SDK and AVD management, please use Android Studio.
For command-line tools, use tools/bin/sdkmanager and tools/bin/avdmanager