Do not package 64 bit libraries

[blagoev]

Currently android runtime is 32bit only on arm and x86. When a plugin brings its own native library it might contain 64bit builds. This is quite possible since most libraries authors are advised to support all ABIs available.
When Android installs the application it checks for the existence of any 64bit library in the package and marks the application as 64 bit compatible. This requires all other libraries to provide 64bit versions of their so files.

One possible fix is to not package any 64bit native libraries in the final application package. (until we provide 64bit versions of the runtime)

This is related:
NativeScript/nativescript-marketplace-demo#84

[atanasovg]

ping @teobugslayer This is of high importance until we have 64-bit version of the runtime.

[slavchev]

Additionally, #330 provides runtime binaries for ARM64.

[blagoev]

now that we have arm64 we should think how we are packaging the application. Are we going to include this in the package or we will provide a flag in the CLI to optionally enable this?

also if some plugin is 32bit only the app will fail if we package any 64bit lib in the apk so we need to stop the build with an error and warn the user

[slavchev]

Thanks @NathanaelA

Here is an interesting comment facebook/react-native#2814 (comment) discussing the same topic. That guy @corbt has a blog post as well.

[blagoev]

The guidance from Google is to use multiple apks when the apk gets over 50MB in size.

[teobugslayer]

I have created a separate issue with another approach of dealing with this problem: NativeScript/nativescript-cli#1392 Please comment!

[atanasovg]

Let's use the issue @teobugslayer created. Closing this one.