Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Change issue status back to 'Assigned'
Pending code changes (auto-populated)
[ID: 84651]
Select items in the list
[ID: 558956]
[ID: 874707]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
[ID: 85206]
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
Context
What happened
When assembling an application having multiple APK support, the content of the generated file
output-metadata.jsoncan 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.jsonremains 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.jsonapp/build/outputs/apk/debug/output-metadata.json:
https://github.com/jprinet/android-sample-app/blob/main/output-metadata-second.jsonIs this a security related issue?
No