Hi. Well, the history is so far: we hit 64K DEX methods limits again. We did it already two times and managed to bypass it by giving up on some Android plugins or optimizing etc but don't intend to do it anymore because it's clearly a dead end, so we're trying to move to "Multi Dex" building scenario. But when I'm trying to build project using new Gradle build system, it fails with a very known problem: As we know, Google Play Services add the following meta-data to AndroidManifest.xml (in a Assets\Plugins\Android\MainLibProj\AndroidManifest.xml): Resource integer "google_play_services_version" previously was located in "<android-sdk>/extras/google/google_play_services/libproject/google-play-services_lib/" in a "res/values/version.xml" file. But recent modular Google Play Services libraries store this value within a "play-services-basement-x.y.z.aar" library (in a "res/values/values.xml file) . So, it looks like Gradle and/or AAPT is not processing correctly resources from AAR libraries, or AAR files are not given to it. And I don't know who to blame: Unity, Unit-Gradle bridge, Gradle, Android SDK build tools (AAPT) etc? This also gives me a same result if I'm trying to export Gradle project and open it in Android Studio. This happens both in our big and dirty production project and fresh new empty test project with only GooglePlayGamesPlugin-0.9.36.unitypackage imported from official Google Play Services from Unity repo. About my environment: 1. Unity 5.5.1f1 Win64 on Windows 10. 2. Latest just updated Android SDK with latest build tools, platform tools, Android SDK, Support library, Google Play Services etc. Path from logs says that Build-tools version 25.0.2 used (latest available). 3. JDK 1.8.0_102 . 4. Mono 2.0 scripting backend used. 5. Android libraries in a Assets\Plugins\Android\ : play-services-auth-10.0.1.aar play-services-auth-base-10.0.1.aar play-services-base-10.0.1.aar play-services-basement-10.0.1.aar play-services-drive-10.0.1.aar play-services-games-10.0.1.aar play-services-nearby-10.0.1.aar play-services-tasks-10.0.1.aar support-annotations-24.0.0.jar support-v4-24.0.0.aar All of them were selected automatically by Google Play Services Resolver script as latest available from Android SDK (except for support-* - it selected 24.0.0 even if there's more recent 24.x.x or even 25.x.x releases).