Fixed
Status Update
Comments
ga...@google.com <ga...@google.com> #2
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
hm...@google.com <hm...@google.com>
hm...@google.com <hm...@google.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
Description
Context
What happened
When assembling an application having multiple APK support, the content of the generated file
output-metadata.json
can vary, ABI definitions not being ordered consistently.This has a direct impact on the build performances as cacheable Gradle tasks using this file as input won't get the same cache key generated.
Expected behavior
output-metadata.json
remains identicalSteps to reproduce the problem
This is not happening constantly and I had to apply the focus plugin to be able to reproduce. I am aware of other situations where this behavior happened without the focus plugin though.
app/build/outputs/apk/debug/output-metadata.json:
https://github.com/jprinet/android-sample-app/blob/main/output-metadata-first.json
app/build/outputs/apk/debug/output-metadata.json:
https://github.com/jprinet/android-sample-app/blob/main/output-metadata-second.json
Is this a security related issue?
No