IssueTracker

Sorry, this tracker is for issues with the Android OS only. Please use https://support.google.com/ to obtain support for Google products or services.

I've searched for correct issue tracker for 15 minutes and wasn't able to find one. The link you gave doesn't help too.

Even Googlers on your support forum don't know where is the issue tracker for Google Play Services https://productforums.google.com/forum/#!topic/play/dZBSTcEuboA;context-place=topicsearchin/play/google$20play$20services$20issue$20tracker.

Please reopen this issue here or in the right place because basically it's going to /dev/null now.

Sorry, there doesn't seem to be an appropriate place to report bugs with Play Services. But they aren't part of AOSP Android so there's literally no point raising it here - we can't provide help or support for something we don't have the source of.

I can confirm this issue - 100+ dex files in APK and NoClassDefFound errors. I have reviewed ClassLoader and printed DexFile.entries() and there were lots of missing classes(for example android.support.v4.util.*).

I also can supply APK if needed.

I can reproduce this on all Android 5.0 devices I have. This is not instant run issue, also issue is gone if I switch to minSdkVersion 16 (because then only 3 dex files are generated)

Here is important part of build.gradle:

        compileSdkVersion 24
        buildToolsVersion "24.0.0"
        defaultConfig {
            applicationId appId
            targetSdkVersion 24
            versionCode versionNumber
            versionName versionTitle
            multiDexEnabled true
            vectorDrawables.useSupportLibrary true
        }
        dexOptions {
            jumboMode false
            javaMaxHeapSize "6g"
        }
        productFlavors {
            production {
                minSdkVersion 16
            }
            temprorary {
                minSdkVersion 21
            }
        }

Just an update - on Android 6 devices same APK works without problems

I am not sure we can fix this reliably. The issue is that if we were to merge all predexed libraries like I suggested in #6, it would end up creating multiple dex files for the merged libraries with split java packages. This has been an issue prior to N as the dalvik verifier can fail when split java packages are present in multiple dex files.

The "only" thing I can suggest would be to have some preprocessing task to merge some libraries making sure you stay below 65K. Merge enough libraries so you end up below the 100 dex files limit.

This is not awesome to say the least but there does not seem to be alternatives to would reliably work in all cases.