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
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
- SerializedPropertyChangeEvent is invoked when initially binding PropertyFields in custom Editor
- UI Panel is not visible when HDR and STP filter are enabled
- Crash on GfxDeviceD3D11Base::DrawBuffersIndirect when opening a specific project
- OnTriggerExit2D is called in Play mode when undoing component adding
- Builds fail with "Execution failed for task ':launcher:checkReleaseDuplicateClasses'" error when the newer version of the In-App Purchasing package is installed on a specific project
MikDab
Feb 02, 2018 12:42
One more thing - if you're tinkering with the Gradle stuff, I recommend making sure that it syncs properly in Android studio, since if it does not - that means that there are some errors and building from Unity will probably not work either. The setup I posted below resulted in my Gradle and Android studio functioning properly with no errors.
MikDab
Feb 02, 2018 12:37
For those using Unity 2017.3.0f3 and those still experiencing this issue.
I found an option which worked for me:
In android studio, I am using the 4.2.1 Gradle version from https://services.gradle.org/distributions/gradle-4.2.1-all.zip
(this video explains how to upgrade/downgrade Gradle, just plug in the appropriate link where needed https://www.youtube.com/watch?v=soL-S7YAxP4)
(Latest version of Gradle is no good, neither did 4.1.something work)
SDK build tools version (what I could gather from other sources): 25.2.5
Up until this point I could still not build my app successfully, and the reason was because that I used the latest JDK version (9.0.4). Since Android Studio has its own inbuilt JDK, in Unity I changed the JDK path to Android Studio/jre.
If that does not work, I suggest downgrading the JDK manually. Hope this helps!
dmart331
Feb 01, 2018 17:06
Still an issue with 2017.3 and the patches.
ojelibalon
Feb 01, 2018 16:30
I am also having the same issue on 2017.3.0f3
Marcos-Elias
Jan 31, 2018 15:31
Same here on 2017.3!
Lots of hours lost.
Khurshed
Jan 31, 2018 05:19
I also have this problem while building for Android.
OOSolo
Jan 29, 2018 04:51
This bug has regressed and needs to be reopened. Repros in 2017.3.0.f3
ctuelho
Jan 19, 2018 01:21
Still a problem with most recent unity and sdk versions....
porandojin1
Jan 18, 2018 13:21
still an issue. almost for a year now.
DemonGamesStudio
Jan 10, 2018 13:19
Still an issue for me. I tried the new tools i tried the old tools. Been stuck for days. Going to make a new post, since for some reason this is marked as resolved.