Android demo doesn't pack multiple architectures from Envoy mobile aar

[buildbreaker]

Building the Android demo can only be built with a single architecture.

The current android_binary Bazel rule has a bug (bazelbuild/bazel#8283) where it doesn't pack multiple architectures from aar_imports. Underneath the android_binary, it uses aar_imports for any aar dependencies.

Any Android applications using Bazel depending on Envoy Mobile will have this issue.

[junr03]

A fix for this problem will be included in 0.27. per bazelbuild/bazel#8283 (comment). Is this issue blocking for OSS release, or do we currently have an ok solution? If we have a decent solution we can move this issue to envoy-mobile under 0.2 release.

wdyt @buildbreaker?

[buildbreaker]

We should move to 0.2

[stale]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

[junr03]

@buildbreaker we fixed this with the fat apk, didn't we? If that is the case do you mind commenting and closing?

[buildbreaker]

@junr03 Correct. This is not really that important since we are able to build a fat aar.