I suggest checking out the official Unity3D forum on this issue:
Support for multiple Android applications
And Q / A from there: Too many method references when exporting an Android assembly
Here is a response from a Unity spokesperson:
So the biggest reason we haven't added support to Unity is because it doesn't work. Rather, it usually creates more problems than it solves. If you do not focus only on modern versions of Android, I would advise you to do everything in your power, including deleting and preliminary checking your code before you go through a route with several decks.
If you do not believe me, just check out the well-known limitations of the multi-dex library on the Googles developer page: https://developer.android.com/tools/building/multidex.html#limitations
So, we will do our best to reduce the number of methods to stay within 65K. For example, if you use google-play-services.jar, you can replace it only with the necessary submodules.
It also discusses exporting to Android Studio and creating a project there, but apparently it did not work due to a problem with dex.
In addition, I recommend reading this article about the DEX problem.
Hope this helps. Good luck
source share