You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I confirm this issue, SDKDownload.java needs to be configured to download the latest command-line tools. Changing android-toolslib version to recent latest 30.1.3 showed some used methods have been replaced and removed. Here is a part of the errors after changing the version -
SDKUpdater.java:161: error: method getInstance in class AndroidSdkHandler cannot be applied to given types;
AndroidSdkHandler mHandler = AndroidSdkHandler.getInstance(sdkFolder);
^
required: AndroidLocationsProvider,Path
found: File
reason: actual and formal argument lists differ in length
\SDKUpdater.java:164: error: cannot find symbol
FileSystemFileOp fop = (FileSystemFileOp) FileOpUtils.create();
^
symbol: class FileSystemFileOp
location: class SDKUpdater.QueryTask
Not sure, but does resolving this issue really depend on Gradle upgrade? @codeanticode
Due to removal of Java EE modules in Java 11:
https://jaxenter.com/jdk-11-java-ee-modules-140674.html
This could be fixed by using new new Android SDK Command-line Tools For JVM 9, 10, 11, And Later:
https://www.dev2qa.com/how-to-fix-java-lang-noclassdeffounderror-javax-xml-bind-annotation-xmlschema-when-install-android-sdk/
The text was updated successfully, but these errors were encountered: