Fixed
Status Update
Comments
sh...@gmail.com <sh...@gmail.com> #2
Comment has been deleted.
sh...@pinterest.com <sh...@pinterest.com> #3
Almost 2 months later and this is still broken
hu...@google.com <hu...@google.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
sh...@pinterest.com <sh...@pinterest.com> #5
jb...@google.com What is the update on this?
hu...@google.com <hu...@google.com> #6
What is the status of this item?
as...@gmail.com <as...@gmail.com> #7
This has been fixed on master today (internal ref: ag/2945015) and will be available in the next SDK release.
hu...@google.com <hu...@google.com> #8
Any ETA on next release?
as...@gmail.com <as...@gmail.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.
hu...@google.com <hu...@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
```
sh...@pinterest.com <sh...@pinterest.com> #11
Hi, is there any update to this issue? Thanks.
hu...@google.com <hu...@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?
sh...@pinterest.com <sh...@pinterest.com> #13
Yeah, still not fixed --'
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.
as...@gmail.com <as...@gmail.com> #15
Any updates on this? The help for this command clearly states this argument is supported.
hu...@google.com <hu...@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.
as...@gmail.com <as...@gmail.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
an...@google.com <an...@google.com> #18
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 Koala | 2024.1.1 Canary 6
- Android Gradle Plugin 8.5.0-alpha06
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!
hu...@google.com <hu...@google.com> #19
ma...@gmail.com <ma...@gmail.com> #20
Comment has been deleted.
Description
(I'm creating this bug based on Internal Issue 234414461 .)
Steps to reproduce
app
, setminSdk >= 24
(whenminSdk < 24
, dexing transforms are not incremental)lib
, setcompileOption.targetCompatibility = "11"
(in lower Java versions, nest members do not exist)lib
, write a Java class with nested classes./gradlew :app:mergeLibDexDebug --build-cache
at that location../gradlew :app:mergeLibDexDebug --build-cache
. Many tasks/transforms should have cache hits../gradlew :app:mergeLibDexDebug --build-cache
again. It will fail with:Root cause
Dexing transforms use a desugaring graph to store dependencies among class files for incremental dexing/desugaring.
The desugaring graph's nodes are currently absolute paths, which means after a remote cache hit, it will not be usable and will result in subsequent failed incremental builds.
We were aware of this issue when designing the graph and used a workaround , but (I think) at some point Gradle changed the behavior and it no longer worked.
Potential fix
Make the desugaring graph relocatable. It is a bit difficult because there isn't one single root path to normalize the absolute file paths (instead, there are multiple root paths).
(If we can't work out a solution soon, the temporary measure is to ensure in the first build after a remote cache hit, affected transforms will be non-incremental.)