Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upEnable Multidex support #344
Comments
|
The issue has really high priority as the following steps lead to dex errors:
As we are expecting the customers to use these two plugins a lot, can we raise the priority of this issue. Is there a workaround? |
|
Ok, the problem is caused by the |
|
There is an issue with my nativescript-google-maps-sdk - not sure if it's related dapriett/nativescript-google-maps-sdk#7 The map shows up blank on Android 4.2.2, only thing odd I seem to find in the Android logs are messages like this:
The plugin already limits the dependencies to only |
|
This feature will be enabled for use in android-runtime 2.0, because you will be able not only the |
|
How could I test this out with dapriett/nativescript-google-maps-sdk#7 ? Any examples with multidex support? |
|
@dapriett not yet, but i'll write an article or documentation, that explains all possibilities that come thanks to the static binding generator and how to utilize them. |
The problem
In case the application is using a lot of plugins and compile dependencies, the dexing may fail with
It turns out this is Android limitation:
Android way to fix this
In order to overcome this limitation, here's the official guide how to support multidexing:
https://developer.android.com/tools/building/multidex.html
The idea is to add the following to
build.gradle:Also some changes must be applied in AndoridManifest.xml OR our own
NativeScriptApplicationclass:NativeScriptApplication- inattachBaseContext()method callPossible way to handle this
Maybe NativeScript CLI can pass some flag to build.gradle and based on it we can enable multidexing and call
MultiDex.install(this);