proguard gradle debug build but not the tests

Question

I enabled proguard for the debug build using:

android {
    buildTypes {
        debug {
            runProguard true
            proguardFile 'proguard-debug.txt'
        }
        release {
            runProguard true
            proguardFile 'proguard-project.txt'
            zipAlign true
        }
    }
}

The problem I'm experiencing when I do this is that the gradle build wants to proguard the tests during the proguardDebugTest task as well. I can't seem to modify to get access to this particular task. Is there a way I can proguard the debug apk but not the test apk?

score 18 · Answer 1 · answered Jun 08 '15 at 06:34

runProguard is old. It was replaced with minifyEnabled

With minifyEnabled (and other changes in new versions of gradle) you will may encounter issues where the proguard config works for your debug apk but not for the instrumentation tests. The apk created for instrumentation tests will use its own proguard file, so changing your existing proguard file will have no effect.

In this case, you need to specify the proguard file to use on the instrumentation tests. It can be quite permissive because it's not affecting your debug and release builds at all.

    // inside android block
    debug {
        shrinkResources true  // removes unused graphics etc
        minifyEnabled true
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        testProguardFile('test-proguard-rules.pro')
    }

For me, I needed to add `testproguardFiles()`, and in that file I have the flag `-dontshrink`. — Billy Lazzaro, Jul 28 '15 at 16:08

sschuberth · Answer 2 · 2015-11-05T13:26:41.173

10

Introduce a new build type "derived" from debug specific to the test app that disables ProGuard again like

android {
    buildTypes {
        debugTest.initWith(debug)
        debugTest {
            minifyEnabled false
        }
    }
}

and use that build type for the test app by assigning its name to the testBuildType property

android {
    testBuildType 'debugTest'
}

edited Nov 05 '15 at 13:26

answered Sep 19 '14 at 07:49

sschuberth

28,386
6
101
146

Minor note: gradle nowdays (checked for 2.6) uses `minifyEnabled false` instead of `runProguard false` – Andrey Starodubtsev Sep 17 '15 at 12:36
@AndreyStarodubtsev Thanks, I've adjusted my answer. – sschuberth Nov 05 '15 at 13:26

score 3 · Accepted Answer · edited Sep 19 '14 at 07:06

Put

gradle.projectsEvaluated {
    proguardDebugTest.enabled = false
}

it in your build script.

There are two things to know here:

The general Gradle feature to enable / disable tasks.
The Android Gradle plugin specific deferred creation of tasks in afterEvaluate, so you need to also defer disabling of the task to afterEvaluate.

EDIT:

One small note: It disables the task but fails the build. This is because the :preDexDebugTest task wont run with proguard on. The best solution i've found so far is to have debug specific proguard config. More details here. Create a separate proguard config file, include the regular proguard file like so:

-include proguard.cfg

and add test config. For me it was:

-dontwarn org.mockito.**
-dontwarn sun.reflect.**
-dontwarn android.test.**

proguard gradle debug build but not the tests

3 Answers3

EDIT:

Linked