I just upgraded Unity 2017.2 to 2017.3.0f3 on MacOSX hoping that it'd fix some issues in the Android build workflow.
In 2017.2, I had an issue where my Android SDK tools (v. 2.6.11) was causing an "Unable to list target platform" error message when building, which I solved the issue by following the instructions in this thread:
https://answers.unity.com/questions/1320150/unable-to-list-target-platform.html :
- renamed /Users/Antho/Library/Android/sdk/tools to tools-26.1.1
- downloaded tools v25.2.5 from https://dl.google.com/android/repository/tools_r25.2.5-macosx.zip and extracted them as tools-25.2.5
- ln -s /Users/Antho/Library/Android/sdk/tools-25.2.5 /Users/Antho/Library/Android/sdk/tools
This worked like a hacky charm and I hoped that the 2017.3 update would make that unnecessary by supporting the newer SDK tools. Unfortunately it didn't, and the 25.2.5 tools no longer work either, I get a new error message stating "Android SDK is outdated, SDK Tools version 0.0.0 < 24.0.0." with 3 options:
Cancel / Use Highest Installed / Update Android SDK.
"Use Highest Installed" leads to "Build Failure / Unable to list target platforms. Please make sure the android sdk path is correct. See the Console for details." (the sdk path is correct)
"Update Android SDK" leads to "Build failure / Unable to update the SDK. Please run the SDK Manager manually to make sure you have the latest set of tools and the required platforms installed. See the Console for details."
I have Android Studio installed with all the most recent SDK versions & tools.
In my Unity Preferences, I use the following as SDK path: /Users/Antho/Library/Android/sdk
I use Android Studio's built in JDK: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home
And left the NDK path empty. That config worked fine on 2017.2.
Should I roll back to 2017.2? Or is there something in my Android config I need to change/downgrade? I'm targeting Android's API level 22.
↧