Failed to update Android SDK package list error when using SDK installed with unity.

Checking Unchecking didn't help.
Removing environment variables didn't help.
But adding the "/" did help.

Thank you!

 

I just did this on OSX and now it works. I hope someone at Unity is listening.

 

I got the same error on MacOS using Unity 2019.4.18.f1 and after a lot of messing around I think I might have figured it out.

At times ( don't know why ) Unity ( or something else ) starts resetting the JAVA_HOME environment variable to string empty when you start Unity. So even if you set JAVA_HOME via console or .bashrc/.zshrc depending on MacOS version it still doesn't work.

I think that adding "/" to the external tools SDK path just forces Unity to set the path again which makes it work for a while. And after that if it stops working you can just remove the "/" save the path and it will work again for some time.

What permanently fixed it for me was the post from using JustAnotherDude's suggestion and adding an editor script to the Editor folder that changes the JAVA_HOME environment variable every time Unity starts so there are no more surprises.

Here's my version for MacOS

Code (CSharp):

1. using UnityEditor;
2. using System;
3.  
4. public class UnityJavaSDKFIx : MonoBehaviour
5. {
6.  
7.     [InitializeOnLoadMethod]
8.     static void SetJavaHome()
9.     {
10.  
11.         Debug.Log("JAVA_HOME in editor was: " + Environment.GetEnvironmentVariable("JAVA_HOME"));
12.  
13.         string newJDKPath = EditorApplication.applicationPath.Replace("Unity.app", "PlaybackEngines/AndroidPlayer/OpenJDK");
14.  
15.         if (Environment.GetEnvironmentVariable("JAVA_HOME") != newJDKPath)
16.         {
17.             Environment.SetEnvironmentVariable("JAVA_HOME", newJDKPath);
18.         }
19.  
20.         Debug.Log("JAVA_HOME in editor set to: " + Environment.GetEnvironmentVariable("JAVA_HOME"));
21.  
22.     }
23. }

 

What the F***... This works. Unity....

 

This fixed my problem. How can Unity be so ignorant of this kinda issue on mac?

 

I don't think it's the "/", I think adding the slash just forces Unity to update the path. You might run into this problem again later and removing the slash will fix it ( it happened for me ).

 

I just solved the issues by changing the API Compatibility Level from .NET Standard 2.0 to .NET 4.x.

It worked for me

 

hi this a simple and shor video that show what to do in a minute

 

I had save issue on Mac.
What I did is first removed java, which I installed separately from oracle site.
Then set JAVA_HOME to PlaybackEngines/AndroidPlayer/OpenJDK folder from code

Code (CSharp):

1.     static void SetJavaHome()
2.     {
3.         //Debug.Log(EditorApplication.applicationPath);
4.  
5.         Debug.Log("JAVA_HOME in editor was: " + Environment.GetEnvironmentVariable("JAVA_HOME"));
6.  
7.         string newJDKPath = EditorApplication.applicationPath.Replace("Unity.app", "PlaybackEngines/AndroidPlayer/OpenJDK");
8.  
9.         if (Environment.GetEnvironmentVariable("JAVA_HOME") != newJDKPath)
10.         {
11.             Environment.SetEnvironmentVariable("JAVA_HOME", newJDKPath);
12.         }
13.  
14.         Debug.Log("JAVA_HOME in editor set to: " + Environment.GetEnvironmentVariable("JAVA_HOME"));
15.     }

as suggested here: https://stackoverflow.com/questions...te-android-sdk-package-list-unity-2019-2-10f1

That fixed my issue.

 

Thanks, works

 

Glad it helped so many people! it's a nightmare having your plan hanging because of a minor issue...

 

Don't think I saw this solution here, but it worked for me. Apparently a problem arises if your editor files are inside "C:\Program Files\..." on a windows machine. The space in "Program Files" messes everything up once certain plugins need to access the tools there. Moving it to a different directory may fix it for you.

Resolved - Failed to update Android SDK package list - Unity Forum

 

TODAY,

Just disabling Android SDK checkbox and adding '/' at the end of sdk path fixes the problem for me.

 

After struggling with issue for 2 days and applying different solutions (which also works few hours) came to know that,
above one is the main cause of error.
Use of editor script works perfect for me. Thanks for saving time.

 

This is still a problem in 2020.3.3 quite shocking really.

 

Wow. This is just unbelievable!! This solution really works! Thanks a lot.

FYI;
I'm using Unity 2020.3.19f (macOS), Firebase, Google External Dependency 1.2.166.
When clicking "Force Resolve" I got this error:

Trying stuff like setting JAVA_HOME and java in PATH doesn't help. But unchecking and checking again those sections related to Java path in Unity External Tools preferences does solve the problem!


Edit 1: It stops working again. Hmmm.... :|

Edit 2: On my machine (macOS), I install OpenJDK via Homebrew, then no more "unable to locate java runtime" error when running "Force Resolve".

 

this works for me too. haha. I think this is engine bugs.

 

This problem still occurs on Unity 2021.2, and the "uncheck and recheck the java checkboxes" thing still fixes it. Hard to believe. Is there a bug tracking this issue?

 

when i build my android project then Daemon error occurred , help me. I use playfab, mopab and Facebook SDK in my project

 

same but JDK! MacOS Catalina

 

follow this https://javatutorial.net/set-java-home-windows-10 It worked for me

 

I had the same error (unity Failed to update Android SDK package list)
Solved by clicking the play button. Then >> File >> Player sittings >> it will automatically update the list then select the latest API >> click the play button again then the problem is solved forever

 

Thank you so much, It works for me Unity 2019.4.33f1

 

using the Open JDK that comes with Unity I was unable to force resolve the android dependencies.

 

Thanks a lot sir! Acutally worked

 

Same for me. Thank u! (Unity 2020, Mac)

 

thank you very much

 

this solution worked for me in case anyone still having the same issue

 

Just came by to say using Unity 2020.3.24f1 on Mac OS Big Sur 11.6.5 I got hit by this (previously was able to build), and the trailing "/" appears to be the solution for me.

The only thing I'd add/ask is how did you figure this out?!

 

The fact that this is still a problem for unity is surprising. Especially because we know they comb these forums rigorously.

 

I am really sorry to tell this, but the fixes/solutions described here are not really fixes. Just workarounds - sometimes it doesn't even work this workaround with the checkboxes (it's ridiculus what one has to do, just to get the android sdk working).

Real fix needs to come from Unity.

Anyways... what worked lately for me (before was just unchecking the boxes, restart and check again). Now I unchecked the JDK and added a "\" symbol at the end. Then from the dependency manager -> force resolve. It worked.

 

These two steps helped me to run my project on MacOS and export Android build:

 

Still happening on 2020.3.35 LTS.

 

I have upgraded my project to Unity 2021.3.3f1 LTS version then after above settings worked for me and now I have open and closed Unity hundred times after this and it was working proper and I can export Android build.

 

Can Unity PLEAAAEEAASE fix this! While some of the above workarounds does work, you have to redo them every time you open your Unity Editor. SO annoying

 

yes - we have to do every time and this is annoying too.
may be in the next release of Unity, this thing will get fixed.

 

That solve the issue! THANKS

 

Thanks!

 

Found a fix here that helped me
https://stackoverflow.com/questions...te-android-sdk-package-list-unity-2019-2-10f1

1. Project Settings > Player > Target API Level: Change "Automatic" to "Android 11" (or else)
2. Play once and Stop.
3. Change target api level to Automatic.

 

This helped me, but i didn't re-install or added JAVA_HOME env variable.
Steps:
1. Uncheck Preferences -> External Tools -> JDK Installed with Unity
2. Replace with C:\Program Files\Java\jdk[whateverversion]
3. Try to build (build fails and throws some error)
4. Check Preferences -> External Tools -> JDK Installed with Unity
5. Now the path should be Unity's own again
6. Build will work now

 

this worked for me lmao this is crazy

 

I believe there's still a bug here on (latest) macOS (Intel build of 2022.2.11f1) -- possibly only occurs when the path contains a space.

In my case, Unity installs are on RAID'd drive that's mounted at:

/Volumes/Working Data/....

The paths are correct but the error persists; if I run the commands just as they're spit out in the console errors, they fail (due to space), but if I escape them properly they work fine (and the Android SDK, etc. is all there/located as expected).

 

problem fixed here :

 

I can actually confirm, for certain, that there is still a bug related to this issue -- but it appears to be a macOS-specific issue, and only occurs when the path name contains a SPACE.

My Unity editors are installed onto a volume that is mounted to

/Volumes/Main Data/UnityEditors/**

-- as long as that space exists, there's nothing you can do (I tried a multitude of things) that will get the Unity build process to work with the path, which appears to not properly escape the space.

Attempting to manually escape the path does not appear to resolve the issue -- the input (path) is probably getting sanitized, essentially un-escaping the path in this scenario.

Copying the

AndroidPlayer/**

contents to

~/Desktop/AndroidPlayer/**

and then setting the paths appropriately (to reference that location, which has no spaces) in the Unity preferences DOES resolve the issue.

I'm relatively confident that there IS a Unity-side bug related to having spaces in the path.

That said, even Android Studio warns "spaces in the path may cause issues" when you open it; and you do need to open Android Studio to set it to reference the new paths & to download the appropriate SDK versions (at least if you're exporting the Android project, which I was).

 

I have the same issue on 2022.14 I tried everything but nothing worked for me...

It's building on 2020 without any problem but when I upgraded to 2022 I got this annoying issue
Is there any other solutions ?

 

My Unity Hub is in C Drive but my Unity Editor is in another drive
in my case a solution for me is
1) goto Edit>Preferences

.
2) uncheck all the check boxes and check them again. Copy the address of JDK

.
3) after copy the address uncheck the JDK check box and paste the copied address here manually

.
4) force resolve the android dependency

 

Works for me Thanks

 

I had this problem in macOS even after trying all the solutions.
The problem solver for me was going to my SDK path, then cmdline-tools/xx.xx/bin and right click on "sdkmanager" and clicking open, to permit it to run.
After that, the error disappeared.

 

I had the problem too on a new computer. None of the solutions proposed worked.
I ended up copying the AndroidPlayer folder from my other computer onto the new one.
As I tried to do that, it couldn't copy over all the files because the file paths were too long.
So I used the command line to copy it over using robocopy.
Then finally it worked.

This was all on Unity 2021.3.31.