This question was closed Jan 03, 2018 at 01:19 AM by Antho for the following reason:

Problem is not reproducible or outdated

Question by Antho · Jan 02, 2018 at 08:43 PM · android build android build android sdk

Unity 2017.3.0f3 / Android SDK Tools incompatibility

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.

Add comment · Show 5

Antho · Jan 03, 2018 at 01:21 AM 1

(closing this)

There was an issue in my tools-25.2.5 folder which had missing files. It seems like the error message "Android SD$$anonymous$$ is outdated, SD$$anonymous$$ Tools version 0.0.0 < 24.0.0." happens when the tools folder is found but is corrupted.

udit2910 Antho · Mar 30, 2018 at 05:55 AM 0

that solved your problem... because i am having same problem as you ? if yes then show me the proper way to solve this error. thank you.

Antho udit2910 · May 23, 2018 at 11:08 PM 0

Oh sorry I didn't realize this question got so many followers. I just re-downloaded the Android tools v25.2.5. As mentioned in my comment the specific error I was getting ("Android SD$$anonymous$$ is outdated") was due to missing files, but I have no idea how they disappeared.

/edit and FWIW I'm still using 2017.3.1f1 and the very latest Android release, I still have to use Android Tools 25.2.5 in order to successfully export my project (and avoid "Unable to list target platforms"). That bug's been around for over a year, it's a real bummer.

Show more comments

Answers Answers and Comments

160 People are following this question.

Unity 2017.3.0f3 / Android SDK Tools incompatibility

0 Replies

Follow this Question

Related Questions