Android SDK does not include your Target SDK of 28

I've seen a few posts with the same issue, but I haven't found a solution anywhere and this is driving me crazy. What am I missing here?
I've installed the android SDK from Unity hub (latest version, up to Android 29)


I've set all paths to their recommended defaults


I've had Target API on 'highest', but on startup it mentions jetifier and suggests setting it to 28 (which should work, so why not?)


But then on build...

I've seen people suggest to install Android Studio and just set SDK paths to the SDK that comes with that, but doesn't that defeat the purpose of having an Android component installed from Unity Hub?

 

Thanks, manually setting it to version 29 did the trick. My bad; I was under the assumption higher versions covered lower ones. Jetifier is mentioned on startup: When my project is set to use "highest installed" Android SDK:

(which should be 29) it seems to default to 25, so when I launch the editor I get this warning:

If I click "yes" I end up with the target SDK set to 28 and the original problem ensues (since I have 29 installed, not 28). But manually setting it to 29 solved the issue! It would seem that there is a bug with the "Automatic (highest installed)" setting for Target API Level (defaulting to 25). And Jetpack enabling switching to 28 instead of 29 isn't ideal either of course.

 

Thank you very much
I have been fighting with the same issue for some time now, and it were starting to drive me crazy, but this thread helped me solve the problems I had with this.

 

Which 2019 LTS contains android 29?
2019.4.18 installs with 28 I thought and complains about Jetpack (AndroidX). I have no clue what that is about or if any plugins are at fault

When I say set it to 28 it throws a warning:
Failed to determine the most recently installed Android SDK version. Please report this as a bug with the version of Unity you are using at: https://github.com/googlesamples/unity-jar-resolver/issues Resorting to reading a fallback value from the editor preferences GooglePlayServices.PlatformVersionFallback: 25

 

Got similar issue with 2020.2.1f1 after importing Facebook-sdk-9.0.0.
Target API Level to Automatic(highest installed) fixed the issue.

 

Gracias, me estaba volviendo loco!!

 

So a few versions later, it seems this is still happening: manually setting the Player Settings target to API 29 is required, because 'Automatic "highest installed" ' still sets it to 25 (very much *not* the highest installed, which still triggers a Jetpack compatibility error).
I reckon you stopped following this thread @JuliusM , since you haven't commented after stating this is not a bug, but you might want to reconsider that assessment, because this definitely is.

 

I ran Into the same issue just now. I had to manualy select my target to 29. Thank you for all of your help!

 

how to set manually

 

Go to Player Settings -> Select Android -> Other Settings -> For Target API select API 29 (As of now API 30 is recommended at the time of this response)

 

you must download target android sdk like this

Notice:The sdk directory must be in unity

 

Hm, I think this confuses the issue... this thread is not about how to install other versions of Android; it's about Unity's "target level: highest" has unity point to a missing SDK, and how manually setting it to an installed one fixes this. Installing the missing SDK would obviously also help, but is not per se the quickest way to get past this issue (especially since the above requires you to also install Android Studio). You can install Android SDK's directly via Unity, but that might run into Administrator right issues... there is a thread on how to solve that (by writing a small .cmd file with a few instructions) https://forum.unity.com/threads/and...itional-sdk-platform-issue-workaround.963626/

just scroll down to @skdev3 's post to see what that .cmd file should look like

 

How did you get to this UI?

 

that's Android Studio

 

Grappled with this issue for about an hour. Wound up uninstalling / reinstalling every Unity installation on my machine, which also worked.

Just mentioning it here in case people can't find another workaround.