title: What is ndk.abiFilters doing under the hood?
body: <p>I have some native libraries (.a) that I'm packaging into an Android library (AAR) as .so's, but they only support 32-bit and 64-bit ARM, so in my AAR's build.gradle defaultConfig, I have:</p>
  <pre><code>    ndk {
  
          abiFilters 'armeabi-v7a', 'arm64-v8a'
      }
  </code></pre>
  <p>And sure enough, my native .so's end up in the AAR under <code>&lt;AAR&gt;/jni/&lt;ABI&gt;/blah.so</code></p>
  <p>But when I add my AAR as a dependency for an APK, those .so's do not end up getting packaged into my APK.</p>
  <p>UNLESS I also add the above <em>ndk</em> block to the defaultConfig of the APK's build.gradle.</p>
  <p>Can anyone explain what is/isn't happening here? I like to distribute my AAR locally within my company, without requiring them to add that <em>ndk</em> block to their APK build.gradle files.</p>