Fixed
Status Update
Comments
de...@squareup.com <de...@squareup.com> #2
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
dy...@google.com <dy...@google.com>
ju...@google.com <ju...@google.com>
ac...@google.com <ac...@google.com> #3
Almost 2 months later and this is still broken
de...@squareup.com <de...@squareup.com> #4
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
de...@squareup.com <de...@squareup.com> #5
jb...@google.com What is the update on this?
de...@squareup.com <de...@squareup.com> #6
What is the status of this item?
bi...@google.com <bi...@google.com> #7
This has been fixed on master today (internal ref: ag/2945015) and will be available in the next SDK release.
de...@squareup.com <de...@squareup.com> #8
Any ETA on next release?
bi...@google.com <bi...@google.com>
ga...@google.com <ga...@google.com> #9
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.
bi...@google.com <bi...@google.com> #10
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
```
de...@squareup.com <de...@squareup.com> #11
Hi, is there any update to this issue? Thanks.
ga...@google.com <ga...@google.com> #12
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?
hu...@google.com <hu...@google.com> #14
Can't believe this still isn't fixed 2 years later for a command line utility that sits on the main dev site.
Description
DESCRIBE THE ISSUE IN DETAIL:
With the following project structure:
app
modulelibrary
with some classes defined that also uses kapt/dagger2feature
which depends onlibrary
, and makes use of code fromlibrary
.Launching an activity from the
feature
module causes aNoClassDefFoundError
when trying to instantiate the class(es) defined in thelibrary
module.This only seems to happen when Dagger2 is applied to the
library
module and when code is generated via kapt. If all dagger-related code is removed from thelibrary
module then the class loading works fine. When dagger2 is applied it is actually also possible to instantiate the classes that are generated by dagger, despite the manually-defined classes being absent from the dex path.A project that reproduces this error is available here:https://github.com/dellisd/manifest-boom/tree/dagger-wtf (on that particular branch).
Another behaviour of this issue is that changing the app deploy method from "Default APK" to "APK from app bundle" fixes this issue in that project, however the same problem has been observed in other larger projects when using "APK from app bundle". It's been difficult to reproduce in a smaller project, but presumably it is related to the issue described here.
STEPS TO REPRODUCE:
ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE
ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)
The output from these lines of code:https://github.com/dellisd/manifest-boom/blob/dagger-wtf/feature/src/main/java/com/example/manifestboom/feature/FirstFragment.kt#L26-L36
IMPORTANT: Please readhttps://developer.android.com/studio/report-bugs.html carefully and supply
all required information.
Studio Build: 2021.3.1 RC 1, #AI-213.7172.25.2113.8913347 Version of Gradle Plugin: 7.3.0-rc01 (also observed on 7.2.2) Version of Gradle: 7.4 Version of Java: 11 OS: macOS