Fixed
Status Update
Comments
sp...@google.com <sp...@google.com> #2
After offline discussion with Xav:
The abiFilters for the features and the base should be the exact same (not just subset of base). In 3.4, the base module should publish its abiFilters to the features. The features should use these published abiFilters, and there should be an error if the feature modules try to specify abiFilters of their own.
The abiFilters for the features and the base should be the exact same (not just subset of base). In 3.4, the base module should publish its abiFilters to the features. The features should use these published abiFilters, and there should be an error if the feature modules try to specify abiFilters of their own.
sp...@google.com <sp...@google.com>
as...@nexteducation.in <as...@nexteducation.in> #3
i have a optional dynamic feature module with abiFilters (arm64-v8a, armeabi-v7a) alone, and mandatory feature module with abiFilters (arm64-v8a, armeabi-v7a, x86, x86_64), while generating .aab file using android studio am getting below error.
All modules with native libraries must support the same set of ABIs, but module ‘base’ supports ‘[ARM64_V8A, ARMEABI_V7A, X86, X86_64]’ and module ‘zoomISV’ supports ‘[ARM64_V8A, ARMEABI_V7A]’
All modules with native libraries must support the same set of ABIs, but module ‘base’ supports ‘[ARM64_V8A, ARMEABI_V7A, X86, X86_64]’ and module ‘zoomISV’ supports ‘[ARM64_V8A, ARMEABI_V7A]’
Description