And this happens even in a NEW Project, not just in this one. It doesn’t affect playing game, building, or any other tasks, but I want to know:
why is it happening, and
what happens if I don’t fix this?
My Unity Editor version is 22.3.14f1, project template was 2D, and My Seats(I mean, License) is Personal.
It would be the pleasure of any answers. Thank you for reading!
Thanks. I check the log file, and I find out that several Android SDK files had been opened. I think, as the thread below says, it seems to be an Android SDK issue.
@Tomas1856 Thanks for the recommendation. Do you have any documentation/forum links to provide more info about this Google server issue, or when it might be fixed? Thanks!
I am seeing this in 6000.0.30f1, which just released in December '24. Another user reported seeing it in 6000.0.33f1. Sounds like the issue is more related to the version of the underlying Android SDK tools than the Unity version. I did find this SO post about the error outside of Unity, where a user linked to a blog post about fixing the issue on Windows. I haven’t tried that solution yet, but it looks like they’re basically suggesting reinstalling Android SDK (outside of Unity). Reinstalling thru Unity Hub might work also, idk. Again, @Tomas1856, any additional info to which you can link would be very helpful.
From looking at the UnityEditor.Android.AndroidSDKTools source code, it looks like the AndroidSDKTools.ListComponentsVersions() method passes a list of warnings to ignore to .RunAndroidSdkTool(). This list does include "Errors during XML parse:" and "Additionally, the fallback loader failed to parse the XML.", but only if the environment variable UNITY_THISISABUILDMACHINE is set to 1. I’m curious why Unity would ignore some build warnings on build machines but not on user machines. Maybe these XML warnings should be moved out of that condition, so that it is ignored on all machines, not just build machines?
I haven’t been able to find any other info about why the encapsulated Android SDK sdkmanager tool logs this warning in the first place. I can run the command manually with --list --verbose, but I don’t see any other helpful logs in that output.
@Tomas1856 Just following up regarding my findings above. What do you think about my suggestion of suppressing those two warnings on all machines, given that they are not actionable?
Please wait until Unity updates the command line tools to 16.0 (should be pretty soon), these warnings might be gone then. We ignore these messages on Unity CI, since there are strict rules for unexpected messages.
But we don’t want to silence these messages completely, since we don’t know is there any side effect to them.
