java.lang.UnsatisfiedLinkError aab build broken

Environment

mutliple versions seems to be affected at least up to

Installed
Android SDK : 29
Android SDK Build-Tools: 29.0.3
node.js : 10.21.0
nativescript : 6.7.8

Error
Over the time we disabled all "optimize" features because all those seems to be bugged..
Since our version 0.3.2 we went forward and enabled .aab builds.

Now we get following error reports.

Fatal Exception: java.lang.UnsatisfiedLinkError
dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.xxx.mobile-tFMIkE3egIQbK2hZc5zevg==/base.apk"],nativeLibraryDirectories=[/data/app/com.xxx.mobile-tFMIkE3egIQbK2hZc5zevg==/lib/x86, /system/lib, /vendor/lib]]] couldn't find "libNativeScript.so"


Fatal Exception: java.lang.UnsatisfiedLinkError
dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.xxx.mobile-QNIyApCG7KlgDAGIJkBlmA==/base.apk"],nativeLibraryDirectories=[/data/app/com.xxx.mobile-QNIyApCG7KlgDAGIJkBlmA==/lib/arm64, /system/lib64, /vendor/lib64, /system/product/lib64]]] couldn't find "libNativeScript.so"

Theres not a single error in our build pipelines, but still the build process seems not to link the needed library correctly..
If the error rate increases further we also need to disable this again, truely disappointing.

To Reproduce
active aab build, deliver to customers

Expected behavior
not crashing

从 Android AAB 构建和原生库打包路径入手，以报告的 java.lang.UnsatisfiedLinkError 和缺少 libNativeScript.so 作为失败点。通过启用 AAB 构建并将其交付到客户设备来复现；当生成的 AAB 包含所需的原生库，并且在报告的架构上不再崩溃时，即视为完成。