New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 861755 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: 2018-07-09
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Building app bundles should automatically choose whether to store shared libraries compressed or uncompressed

Project Member Reported by vollick@chromium.org, Jul 9

Issue description

I ran into a situation where I was creating an apk and I'd included a .so by using loadable_modules and at build time, I got an error that I had inconsistently set whether the apks in the bundle should compress their shared libraries.

I fixed this by making them consistent (by explicitly adding "uncompress_shared_libraries = true" to my new apk), but it would be nice if this setting were determined by the main apk and applied automatically to the others.

cc'd Tibor and David who know more about this issue (please let me know if the details here are wrong).
 
Labels: Pri-3
NextAction: 2018-07-09
Downgrading P2s that haven't been modified in more than 6 months, which also do not have a component or owner.
Status: Untriaged (was: Available)
Available, but no owner or component? Please find a component, as no one will ever find this without one.

Sign in to add a comment