Search Issue Tracker
Fixed in 2019.2.X
Votes
19
Found in
2019.2.0a1
2019.2.0a7
2019.3.0a1
Issue ID
1136069
Regression
Yes
[Android] CommandInvokationFailure appears in console when inspecting the API levels in Player Settings if using Bundled SDK
To reproduce this issue:
- Install either Unity Editor 2019.3 or 2019.2 using the HUB
- install the Android Module and the Android SDK and NDK with the module
- start a new project
- set the platform to Android
- Open Player Settings
- Open the Other Settings section
- Inspect the Minimum API Level and Target API Level fields
Expected Result:
You can change the API levels and no errors appear in the console.
Actual Result:
The fields display "Getting API Levels..." and an error appears in the console:
CommandInvokationFailure: Failed to update Android SDK package list.
E:/Unity/Unity Versions/2019.2.0b1/Editor/Data/PlaybackEngines/AndroidPlayer\SDK\tools\bin\sdkmanager.bat --list
stderr[
Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema
at com.android.repository.api.SchemaModule$SchemaModuleVersion.<init>(SchemaModule.java:156)
at com.android.repository.api.SchemaModule.<init>(SchemaModule.java:75)
at com.android.sdklib.repository.AndroidSdkHandler.<clinit>(AndroidSdkHandler.java:81)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:73)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(Unknown Source)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(Unknown Source)
at java.base/java.lang.ClassLoader.loadClass(Unknown Source)
... 5 more
Reproducible in 2019.2.0a4, 2019.2.0b1, 2019.2.0b10 and 2019.3.0a10
Cannot reproduce in 2019.1.8f1
-
ahmedaniss
Jun 07, 2021 14:30
-
ahmedaniss
Jul 22, 2020 05:30
problem fixed here : https://youtu.be/nECvvVe7gS8
-
cozyurt_unity
Jul 13, 2020 10:31
kedi ve köpek mamaları uygun fiyatlar kaliteli ürünler http://www.patilimama.com
-
minhchanh991
Aug 27, 2019 10:52
The problem is backkkk
-
mpjunior_unity
Aug 26, 2019 01:22
Hi, is the ticket already reopened?
Here I just upgraded to 2019.2.2f1, the problem remains.regards.
-
bithero-no
Aug 24, 2019 18:04
Still an problem in 2019.2.2f1. Updated two projects to 2019.2.2f1 today, and the projects settings dosn't work and I still get the error in the console.
Was able to see the projects settings after manually setting the android versions after opening the ProjectSettings file in a texteditor.
AndroidMinSdkVersion: 19
AndroidTargetSdkVersion: 28The android versions dropdowns will still not show up in projects settings, but I can atleast adjust all other settings.
-
Hoglet
Aug 22, 2019 16:39
Still present in Unity 2019.2.2 !!! So dear unity reopen the issue...
-
alphadogware
Aug 22, 2019 12:05
I am running Mac with Java 8 update 221 on 2019.2.2f1 and am having this issue.
-
christopherclarke
Aug 20, 2019 12:25
I have a Mac trying to build Oculus Android content and this happens from 2019.2 and above. I have down graded to 2019.14f until this is fixed completely with no workarounds
-
Irzorg
Aug 16, 2019 13:06
Upgrade Unity from 2018.3 to 2019.2 and problem appears
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Screen Space Ambient Occlusion is ignored when toggling "Post Processing" visibility in the Scene window overlay
- “RenderTexture.Create failed: requested size is too large.” errors are thrown and the Inspector window is black when selecting a CubemapArray texture
- Crash on AMDUnityPlugin.DLL in specific built project when using FSR2 upscaler
- RenderObjects does not have any Depth texture bound when Event is set to AfterRenderingPostProcessing
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
Resolution Note (fix version 2019.2):
The Android command line tools do not support Java versions higher than 8 at this time. Having Java 9 or 10 installed may cause this error to occur. The recommended course of action is to uninstall Java 9 or 10 and to only have Java 8 installed on your machine.