Fixed
Status Update
No update yet.
Comments
lb...@gmail.com
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
cm...@google.com
je...@google.com
cm...@google.com
Almost 2 months later and this is still broken
lb...@gmail.com
Since there is no progression, I wanted to share our quick-fix for the issue.
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
lb...@gmail.com
jb...@google.com What is the update on this?
cm...@google.com
What is the status of this item?
lb...@gmail.com
This has been fixed on master today (internal ref: ag/2945015) and will be available in the next SDK release.
cm...@google.com
Any ETA on next release?
lb...@gmail.com
Still broken and not updated? --package_file argument is not usable in it's current form on 26.1.1 straight from the developer site.
cm...@google.com
Comfirmed that this seems to still be broken. Can we have an update please?
```
(15:58:11) C02W513SHTD8:files aso$ /opt/android-sdk-macosx/tools/bin/sdkmanager --version
26.1.1
(15:58:17) C02W513SHTD8:files aso$ /opt/android-sdk-macosx/tools/bin/sdkmanager --install --package_file=package_file
Warning: Unknown argument --package_file=package_file
```
```
(15:58:11) C02W513SHTD8:files aso$ /opt/android-sdk-macosx/tools/bin/sdkmanager --version
26.1.1
(15:58:17) C02W513SHTD8:files aso$ /opt/android-sdk-macosx/tools/bin/sdkmanager --install --package_file=package_file
Warning: Unknown argument --package_file=package_file
```
lb...@gmail.com
Hi, is there any update to this issue? Thanks.
vm...@google.com
Hi Google. You claim it's been fixed on master, but we haven't had a new release since the broken version 26.1.1. Can you please release the fix?
lb...@gmail.com
Yeah, still not fixed --'
vm...@google.com
Can't believe this still isn't fixed 2 years later for a command line utility that sits on the main dev site.
lb...@gmail.com
Any updates on this? The help for this command clearly states this argument is supported.
vm...@google.com
Has anyone re-tried it?
We switched back to RUN sdkmanager --package_file=$ANDROID_HOME/packages.txt in our Dockerfile back in March of 2021.
lb...@gmail.com
For what it's worth, I did a quick test with the latest CLI: 11076708 (
./sdkmanager --sdk_root="../sdk" --package_file=deps.txt
Deps.txt:
platform-tools
extras;google;instantapps
build-tools;35.0.0-rc3
So perhaps this is now resolved? I haven't tried it with more packages
vm...@google.com
On the APPDATA is for example C:\Users\YourUserName\AppData\Roaming:
%APPDATA%\Google\AndroidStudio-VERSION\options\jdk.table.xml
lb...@gmail.com
@18 On the laptop, I somehow have 9 folders of Android Studio there, even though I use up to 3 versions (stable, beta, canary ).
Choosing on AndroidStudioPreview2022.3 which seems the latest for canary (how is it 2022?), I deleted the file jdk.table.xml there and then started the IDE.
Then it asked me which JDK to use for gradle.
Then as it opened an existing project, it marked plenty of things in red, related to view-binding, as if they don't exist. Restarting the IDE fixed it.
For a new project, the issue of needing to change gradle JDK version is gone.
In any case, the original issue that I talked about needs fixing.
Please also improve the settings and backward compatibility.
Choosing on AndroidStudioPreview2022.3 which seems the latest for canary (how is it 2022?), I deleted the file jdk.table.xml there and then started the IDE.
Then it asked me which JDK to use for gradle.
Then as it opened an existing project, it marked plenty of things in red, related to view-binding, as if they don't exist. Restarting the IDE fixed it.
For a new project, the issue of needing to change gradle JDK version is gone.
In any case, the original issue that I talked about needs fixing.
Please also improve the settings and backward compatibility.
vm...@google.com
This exception is linked with JDK < 17, on studio version using JDK 17. I was able to reproduce it on a sample project with the following configuration:
JDK 11
Gradle 7.2.0
AGP 4.2.2
The project builds properly from the command line and as a workaround, you need to update your project to the most recent AGP/Gradle version that require JDK 17. In any case, a fix will land soon on AS H Canary 2 and will also be cherrypicked on AS G Beta 3. Please feel free to retest the mentioned versions. Thank you
lb...@gmail.com
@20 Can you please offer a quick-fix being offered to us, to update all that's needed to let the project be built?
I see this a lot, that an "old" project (can even be just 1 year old) can't be opened anymore, and requires various manual steps while the IDE doesn't help much at all, showing "random" errors without any useful clue about what's wrong.
Maybe offer for all build-errors (or at least those that IDE fails to offer a good quick-fix, or when we tried its quick-fix, and it still failed) an automatic check that gets added, to upgrade what you've written (gradle and AGP).
I see this a lot, that an "old" project (can even be just 1 year old) can't be opened anymore, and requires various manual steps while the IDE doesn't help much at all, showing "random" errors without any useful clue about what's wrong.
Maybe offer for all build-errors (or at least those that IDE fails to offer a good quick-fix, or when we tried its quick-fix, and it still failed) an automatic check that gets added, to upgrade what you've written (gradle and AGP).
ja...@gmail.com
The same to me (AGP 8.5，gradle 8.x).
Caused by: java.lang.UnsupportedOperationException: PermittedSubclasses requires ASM9
at org.objectweb.asm.ClassVisitor.visitPermittedSubclass(ClassVisitor.java:281)
at org.objectweb.asm.ClassReader.accept(ClassReader.java:707)
at org.objectweb.asm.ClassReader.accept(ClassReader.java:425)
at com.android.build.gradle.tasks.DependenciesAnalyzer.visitClass(DependenciesAnalyzer.kt:70)
This issue is because:
class DependenciesAnalyzer {
private val asmVersion = Opcodes.ASM7
}
Caused by: java.lang.UnsupportedOperationException: PermittedSubclasses requires ASM9
at org.objectweb.asm.ClassVisitor.visitPermittedSubclass(ClassVisitor.java:281)
at org.objectweb.asm.ClassReader.accept(ClassReader.java:707)
at org.objectweb.asm.ClassReader.accept(ClassReader.java:425)
at com.android.build.gradle.tasks.DependenciesAnalyzer.visitClass(DependenciesAnalyzer.kt:70)
This issue is because:
class DependenciesAnalyzer {
private val asmVersion = Opcodes.ASM7
}
Description
Example attached here.
Please have a better backward compatibility on the IDE, offer proper information that we can do something about it, and offer a quick-fix for each case that is known.