Fixed
Status Update
No update yet.
Comments
ga...@google.com
sp...@google.com
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
ga...@gmail.com
Almost 2 months later and this is still broken
hu...@google.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
hu...@google.com
jb...@google.com What is the update on this?
au...@google.com
What is the status of this item?
hu...@google.com
This has been fixed on master today (internal ref: ag/2945015) and will be available in the next SDK release.
an...@google.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.
Description
DESCRIBE THE ISSUE IN DETAIL:
STEPS TO REPRODUCE:
Expected
Modifying manifest overlay files does not invalidate configuration cache.
Actual
Files such as
constraintlayout/constraintlayout-compose/src/release/AndroidManifest.xmlandconstraintlayout/constraintlayout-compose/src/testDebug/AndroidManifest.xmlare considered input to the configuration cache and modifying them will cause configuration cache to be invalidated.Gradle marks the reader ashttps://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:build-system/gradle-core/src/main/java/com/android/build/gradle/tasks/ProcessLibraryManifest.kt;l=300
com.android.build.gradle.tasks.ProcessLibraryManifest$CreationAction$configure$2which I think it is coming from the following line: