implementation), but supports FLAT. In FLAT output mode, the output is dumped in a format that resembles that of the dex tool itself when you exceed the method limit (flat list of packages proceeded by their package list).

Windows doesn't support the runfile you provided. You can make a .bat file, or provide the different code for Windows:

java -jar [path-to-generated-jar (./build/jar/....)] [filename to inspect]

It doesn't appear that the script supports builds that result in multiple dex files, where classes are segmented into a primary dex file and additional dex files. The script reports only 22K methods, which I believe to be merely the methods from the primary dex (mostly our own application minus libraries.)

The Android tool chain will generate multiple DEX files when your minSdkLevel is Lollipop / 21 since that is how ART deals with library code (one dex per dependency), and also when you have the multidex switch enabled.

The default style still is TREE mode, but a new FLAT mode is added in which the output is dumped in a format that resembles that of the dex tool itself when you exceed the method limit (flat list of packages proceeded by their package list).

Original PR #8 by @brianduff.

Would be great to have a switch that enables a mode which prints only the total method count. I've added this functionality in my fork but it constitutes some rather reaching changes to the code base that I'm not sure fit the pattern you're currently using.

If you have download gradle file in AndroidStudio, then you can replace "distributionUrl=https://services.gradle.org/distributions/gradle-2.4-bin.zip" in gradle/wrapper/gradle-wrapper.properties by "distributionUrl=https://services.gradle.org/distributions/gradle-2.4-all.zip" then the gradle file would not need to download again.

This tip may be useful to the developers in counties which has limited access to gradle.org

Added the ability to enter a directory as input parameter. Directory may contain any supported file types. Script is now printing overall method count from all files after evaluation.

在 https://github.com/Tencent/matrix#matrix_cn 页面单独下载 matrix-apk-canary-0.4.10.jar 失败 浏览器提示:

载入页面时与 d29vzk4ow07wi7.cloudfront.net 的连接中断。

由于不能验证所收到的数据是否可信，无法显示您想要查看的页面。
建议向此网站的管理员反馈这个问题。

Hi i have a JAR which is a library that i have developed for Android devices. I convert the JAR into dex and then run the script. But in my JAR, why are the method counts for android and JAVA packages are involved? These methods are native android and JAVA methods and they don't ship into my JAR. So why are these included for the dex count?

android: 650
        animation: 10
        app: 47
        content: 93
            pm: 11
            res: 4
        database: 18
            sqlite: 8
        graphics: 58
            drawable: 8
        location: 20
        media: 20
        net: 20
            wifi: 8
        os: 38
        provider: 3
        support: 23
            v4: 15
                view: 15
            v7: 8
                widget: 8
        telephony: 41
            cdma: 3
            gsm: 3
        text: 1
        util: 15
        view: 101
            accessibility: 2
            animation: 10
        webkit: 50
        widget: 92
   .........
   .........

    java: 381
        io: 36
        lang: 145
            ref: 3
            reflect: 8
        math: 1
        net: 25
        nio: 4
        security: 9
            spec: 1
        text: 5
        util: 156
            concurrent: 37
                atomic: 8
            zip: 1
    javax: 17
        crypto: 14
            spec: 3
        xml: 3
            parsers: 3
    org: 61
        json: 50
        w3c: 10
            dom: 10
        xml: 1
            sax: 1

Overall method count: 6163

By using %1 it was impossible to use arguments with the bat file. A call like:

dex-method-counts.bat --output-style=flat my.apk

would result in

Exception in thread "main" java.lang.IllegalArgumentException: No enum constant info.persistent.dex.DexCount.OutputStyle.--OUTPUT-STYLE

This change to the bat file passes all arguments to the java call, allowing the above example to work.

mostly gradle scripts to help you publish to maven central.

From here, you'll need to create a gpg key, and a sonatype oss account

then run the commands in the readme file.

https://github.com/mihaip/dex-method-counts/blob/master/src/com/android/dexdeps/DexData.java#L571-L572

static class HeaderItem {
  public static final byte[] DEX_FILE_MAGIC = { 0x64, 0x65, 0x78, 0x0a, 0x30, 0x33 }; // , 0x??, 0x00 };
}

private static boolean verifyMagic(byte[] magic) {
  return Arrays.equals(Arrays.copyOfRange(magic,0,HeaderItem.DEX_FILE_MAGIC.length), HeaderItem.DEX_FILE_MAGIC)
  && magic[HeaderItem.DEX_FILE_MAGIC.length] >= 0x30
  && magic[HeaderItem.DEX_FILE_MAGIC.length+1] == 0x00;
}

Can you make it possible to count inside decompiled APK, so I can easly see if i have reached the limit or not when working with smali without having to recompile?

This updates the Gradle wrapper to the latest version 5.6.4.

Welcome to Gradle 5.6.4!

Here are the highlights of this release:
 - Incremental Groovy compilation
 - Groovy compile avoidance
 - Test fixtures for Java projects
 - Manage plugin versions via settings script

For more details see https://docs.gradle.org/5.6.4/release-notes.html

_{^{Please NO GitHub rebase/squash merges. The changes in this pull request are broken up into meaningful, atomic commits, and my branch should already be up-to-date with the latest target branch. If it isn't, or if you'd like me to combine some or all of the commits, please let me know, and I will make the necessary updates as soon as possible. Thank you!}}

Bug description: No matter how many default package methods there are, the printed result is always 1 for default package methods count. Explanation: The name in line 49 may be "", which means corresponding method is from default package. For the default package methods, code runs into else branch since no child has name "". Therefore, for every default package method, a new Node is created in line 53. For non-first default package method, the newly created Node will always replace the former Node in line 59, and get its count equals 1 in line 63. Overall, method count of default package is always at most 1. I added an else if branch, which avoids making new Node if we already has a Node when the coming method is a default package method.

There's two fixes related to print output and gitignore. But more importantly I've added the ability to compare method counts between the supplied inputs, which prints the difference between the second and first input next to the counts for the second.