Status Update
Comments
ch...@google.com <ch...@google.com> #2
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
ca...@careem.com <ca...@careem.com> #3
ca...@careem.com <ca...@careem.com> #4
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
ch...@google.com <ch...@google.com> #5
ca...@careem.com <ca...@careem.com> #6
ch...@google.com <ch...@google.com> #7
ca...@careem.com <ca...@careem.com> #8
ch...@google.com <ch...@google.com>
ap...@google.com <ap...@google.com> #9
ap...@google.com <ap...@google.com> #10
```
(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
```
ap...@google.com <ap...@google.com> #11
ap...@google.com <ap...@google.com> #12
ap...@google.com <ap...@google.com> #13
ap...@google.com <ap...@google.com> #14
ap...@google.com <ap...@google.com> #15
ch...@google.com <ch...@google.com> #16
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.
ca...@careem.com <ca...@careem.com> #17
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
sg...@google.com <sg...@google.com> #18
Tag for 8.2.39 pushed as well.
an...@google.com <an...@google.com> #19
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Hedgehog | 2023.1.1 Patch 1
- Android Gradle Plugin 8.2.1
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
so...@google.com <so...@google.com> #20
Comment added by automation: A postmortem has been automatically requested for this issue. Please author a postmortem on IRM. See go/android-postmortem-guidance for more context and details, including how to handle the case when this issue does not need a postmortem. If you have any questions not answered by go/android-postmortem-guidance, please email android-hygiene-tpm@, instead of reassigning the fixed bug. Thank you.
Description
Hello, we recently had a broken build resulting in a runtime ClassCastException (
org.jsoup.parser.e cannot be cast to cx2.a
).And this looked weird as the crashing code and module itself (the code comes from an internally published library) has no reference to any
org.jsoup.*
code. (see attachmentoriginal.png
from the class contained in the aar)Looking at the stack trace I opened the smali in the broken apk and I indeed found references of
org.jsoup
class in the primary constructor (attachmentbroken smali.png
) which is odd.Trying to reproduce the problem rebuilding the same code with same configuration the resulted smali in the apk it looks correct (attachment
good smali.png
)I am not sure how I can collect more informations here but I felt I had to file an issue with the little I have. I can privately share the APK and mapping file if needed.
Please note we just updated AGP from 8.1.1 to 8.2.0-rc01 and so R8 (but I am not sure which version is used)