Fixed
Status Update
Comments
xa...@google.com <xa...@google.com> #2
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
sp...@google.com <sp...@google.com> #3
Almost 2 months later and this is still broken
sp...@google.com <sp...@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
Currently, if an Android library dependency has `android:extractNativeLibs` or `android:useEmbeddedDex` set in its manifest, that attribute will be merged into any downstream app's merged manifest.
The desired behavior is to ignore these attributes from dependent library manifests, but doing so might cause some breakages (e.g., some libraries might currently set `android:extractNativeLibs=true` because they package native libraries that don't work correctly without that setting).