transformClassesAndResourcesWithProguardForRelease FAILED

Question

I am trying to Build my Android application with Gradle in console. But getting below error about task ':app:transformClassesAndResourcesWithProguardForRelease':

build.gradle:

buildscript {
    repositories {
        jcenter()
        maven { url "https://jitpack.io" }
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:2.2.3'
        classpath 'com.google.gms:google-services:3.0.0'
    }
}

allprojects {
    repositories {
        jcenter()
        maven { url "https://jitpack.io" }
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

app/build.gradle

apply plugin: 'com.android.application'

android {
    compileSdkVersion 24
    buildToolsVersion '24.0.2'
    defaultConfig {
        applicationId "com.XXX.XXX"
        minSdkVersion 14
        targetSdkVersion 24
        versionCode 1
        versionName "0.1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
        multiDexEnabled true
    }
    buildTypes {
        release {
            shrinkResources true
            minifyEnabled true
            proguardFiles getDefaultProguardFile('proguard-android.txt'),
                    'proguard-rules.pro'
        }
    }
}


dependencies {
    compile fileTree(include: ['*.jar'], dir: 'libs')
    androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', {
        exclude group: 'com.android.support', module: 'support-annotations'
    })
    compile('com.squareup.retrofit2:retrofit:2.1.0') {
        exclude module: 'okhttp'
    }
    compile 'com.android.support:appcompat-v7:24.2.1'
    compile 'com.android.support:design:24.2.1'
    compile 'com.squareup.okhttp3:okhttp:3.4.1'
    compile 'com.squareup.retrofit2:converter-moshi:2.1.0'
    compile 'moe.banana:moshi-jsonapi:2.2.0'
    compile 'com.squareup.moshi:moshi-adapters:1.3.1'
    compile 'com.google.android.gms:play-services-maps:9.6.0'
    compile 'com.android.support:multidex:1.0.1'
    compile 'com.google.firebase:firebase-core:9.6.0'
    compile 'com.google.firebase:firebase-crash:9.6.0'
    testCompile 'junit:junit:4.12'
}

apply plugin: 'com.google.gms.google-services'

gradle-wrapper.properties

distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-3.3-all.zip
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists

./gradlew build --stacktrace

This is the exception I am receiving:

org.gradle.api.tasks.TaskExecutionException: Execution failed for task
':app:transformClassesAndResourcesWithProguardForRelease'.

This issue is coming due to pro-guard enable in the release config of the app. So the solution is either remove pro-guard or put the indicated code of snippet in the link https://readyandroid.wordpress.com/errorexecution-failed-for-task-apptransformclassesandresourceswithproguardforrelease/ — Ready Android, May 02 '18 at 13:34

score 123 · Accepted Answer · edited May 23 '17 at 12:34

123

Try adding this code to your proGuard rules, it worked for me

-ignorewarnings
-keep class * {
    public private *;
}

The answer was posted here: Execution failed for task ':app:transformClassesAndResourcesWithProguardForRelease

edited May 23 '17 at 12:34

Community

1
1

answered Jan 30 '17 at 09:30

John Spax

1,468
1
11
10

12

Even though this seems to work, it would be nice to have an explanation. – Drew Szurko Oct 02 '17 at 21:21
24

But this is of no use since -keep class * { public private *; will keep all your classes from obfuscation, hence proguard of no use here. – Raghav Sharma Jun 13 '18 at 03:19
3

above your code used to my apk decompiled after display original class and code not secure my apk??? – Pankaj Talaviya Jun 25 '18 at 11:46
30

WARNING: Do not use this answer if you wish to keep your code private. – olfek Jun 29 '18 at 18:19
Also, using this made the incompatible with the older phone versions. – red-devil Sep 05 '18 at 08:20
omg how such answers even allowed here, if you do it then it doesn't really make sense using `minifyEnabled` option – user924 Nov 11 '18 at 15:15

ultra.deep · Answer 2 · 2017-05-17T11:40:07.620

65

add this code to ..your-project/app/proguard-rules.pro

 -ignorewarnings

your signed apk will be generated successfully...

Update :

That's better to fix your warning messages using -dontwarn or -keep keys on your proguard-rules.pro... Because if you use (maybe your libraries) java reflection in your code the application will be crashed...

edited May 17 '17 at 11:40

answered Apr 10 '17 at 09:37

ultra.deep

1,699
1
19
23

@Richi, I don't have a *proguard-rules.pro* file. Should I create one manually? It looks like I'm generating on in runtime `release { shrinkResources true minifyEnabled true proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro', 'proguard.cfg' }` – AdamHurwitz Feb 05 '19 at 03:39
@AdamHurwitz Yes, you will have to create this file manually. – CopsOnRoad May 12 '19 at 09:46
1

It's worked in my case to.But I guess it's declared to something as irrelevant.I mean you may get the release apk, but the real problem is still there. – Dorbagna Jun 14 '19 at 10:02

score 8 · Answer 3 · edited Jun 26 '18 at 12:44

8

It worked for me I also had to add following in a pro-gaurd.txt file

#### -- Picasso --
 -dontwarn com.squareup.picasso.**

 #### -- OkHttp --

 -dontwarn com.squareup.okhttp.internal.**

 #### -- Apache Commons --

 -dontwarn org.apache.commons.logging.**

     -ignorewarnings 
-keep class * {
public private protected *;
}

edited Jun 26 '18 at 12:44

Ramesh R

7,009
4
25
38

answered Jul 06 '17 at 17:01

Haris Durrani

119
1
9

10

WARNING: Please don't use this answer if you want to keep your code private/protected – Bilal Ahmed Oct 02 '18 at 07:14
As I understand it "-keep class *" will basically turn off obfuscation and removal of classes. If you want to do this you could easily go to build.gradle and set minifyEnabled to false and remove the proguardFiles line. – FrankKrumnow Dec 21 '18 at 12:54
Is there now way to have minify enabled in the release @FrankKrumnow? – AdamHurwitz Feb 05 '19 at 03:21
Adam I am no proguard - pro myself and struggle with it quite a lot. But please have a look at my new post down there. It contains examples how you can protect certain groups of classes - like classes extending android Views. Maybe this can be a starting point. – FrankKrumnow Feb 06 '19 at 14:54

Brijesh Tanwar · Answer 4 · 2018-04-06T11:20:06.120

7

I have changed nothing just comment

// shrinkResources true
// minifyEnabled true

you don't want to change any proguard file I have already searched for this issue after 2days wasted

edited Apr 06 '18 at 11:20

answered Apr 06 '18 at 05:20

Brijesh Tanwar

143
1
9

All the rest of the suggestions were a fail, this one worked. In my case I had to turn on multidex due to the inclusion of a 3rd party library, as well as upgrade to SDK 27. This error suddenly showed up. Thanks for this answer! – Stephen McCormick Jul 16 '18 at 15:22
5

minifyEnabled launch some kind of encryption for your code. Hacker has easier work when you won't keep this on. It's highly risky to disable it on production-apk file! – Adrian Grygutis Nov 08 '18 at 11:55
Don't use this solution. It is risky – Jack Nov 13 '18 at 13:19
@Gibs what risk in this? – Brijesh Tanwar Nov 15 '18 at 08:24
@Brijesh Tanwar : what if i need encryption?? – Jack Nov 27 '18 at 04:25
@Gibs I think then you have to embrace the pain in the a** that is proguard and filter through it's hundreds of unnessessary warnings and notes to find what's breaking the process without having any clue what you do - just like me ;) – FrankKrumnow Dec 21 '18 at 12:58
This is not resolving the problem since it basically disables ProGuard – Yannick Jun 28 '19 at 19:06

Ayaz Muhammad · Answer 5 · 2018-05-15T09:41:29.660

3

buildTypes {
    release {
        shrinkResources true
        minifyEnabled true
        proguardFiles getDefaultProguardFile('proguard-android.txt'),
                'proguard-rules.pro'
    }
}

Please remove above mentioned code in your gradle. This worked for me. This is only for given problem.

edited May 15 '18 at 09:41

answered May 15 '18 at 07:57

Ayaz Muhammad

138
10

Dear Pang. This error occurred in when i generate signed apk. My senior remove proguard in gradle then this error removed – Ayaz Muhammad May 15 '18 at 08:03
all lines which are mentioned – Ayaz Muhammad May 15 '18 at 09:29

score 1 · Answer 6 · answered Dec 04 '19 at 03:07

1

got this issue due to warning from Android
See comment: https://github.com/flutter/flutter/issues/40218#issuecomment-531047713

add the following rule to /android/app/proguard-rules.pro:
-dontwarn android.**

answered Dec 04 '19 at 03:07

ken

13,869
6
42
36

Ali Bagheri · Answer 7 · 2018-04-08T03:22:36.660

0

Use this code in 'proguard-rules.pro' may be resolve.

-keep class * {
public private protected *;
}

or

-keep class * {*;}

note : above commands ignore obfuscates
can use this instead above for save obfuscates state

-keepnames class * {*;}

edited Apr 08 '18 at 03:22

answered Apr 07 '18 at 08:18

Ali Bagheri

3,068
27
28

having this is the same as removing proguard at all – cesarmax Aug 15 '19 at 18:31

score 0 · Answer 8 · answered Sep 21 '18 at 19:57

0

In Android Studio click "Rebuild Project" in the "Build" menu.

answered Sep 21 '18 at 19:57

Niclin

1
1

FrankKrumnow · Answer 9 · 2019-02-06T14:56:12.560

I have struggled with proguard-rules.pro for quite some time and am by no means a pro here! I am posting my file to show that you should not -keep class * without any parameters as this turns off all obfuscation. You can however protect every class that extends from a certain class or any class that implements a certain interface. You can also protect any class that has a constructor having specific elements. Please note that I did not comment every single line as I am not 100% sure of what everything does - it's more like an educated guess. My project includes ksoap2 (okhttp3, okio, XmlPull) that's what many rules are for.

Maybe this can be a starting point for you - you still may need to put some additional rules for your classes in.

-android
-dontpreverify
-repackageclasses ''
-allowaccessmodification
-optimizations !code/simplification/arithmetic
-keepattributes *Annotation*
-renamesourcefileattribute SourceFile
-keepattributes SourceFile,LineNumberTable

-keep public class * extends android.app.Activity
-keepclasseswithmembers class * extends com.way4net.oner.lifa.plugin.ThemedFragment
-keepclasseswithmembers class * extends com.way4net.oner.lifa.plugin.ThemedActivity
-keep public class * extends android.app.Application
-keep public class * extends android.app.Service
-keep public class * extends android.content.BroadcastReceiver
-keep public class * extends android.content.ContentProvider
-keepattributes Signature #there were 1 classes trying to access generic signatures using reflection emfehlung von proguard selbst

-keep public class * extends android.view.View {
      public <init>(android.content.Context);
      public <init>(android.content.Context, android.util.AttributeSet);
      public <init>(android.content.Context, android.util.AttributeSet, int);
      public void set*(...);
}

-keepclasseswithmembers class * {
     public <init>(android.content.Context, android.util.AttributeSet);
 }

-keepclasseswithmembers class * {
    public <init>(android.content.Context, android.util.AttributeSet, int);
}

-keepclassmembers class * extends android.content.Context {
    public void *(android.view.View);
    public void *(android.view.MenuItem);
}

-keepclassmembers class * implements android.os.Parcelable {
    static ** CREATOR;
}

-keepclassmembers class **.R$* {
    public static <fields>;
}

-keepclassmembers class * {
    @android.webkit.JavascriptInterface <methods>;
}

-dontwarn okhttp3.**
-dontwarn okio.**
-dontwarn android.support.v4.**
#-dontwarn javax.annotation.**
#-dontwarn org.xmlpull.v1.**
-dontnote android.net.http.*
-dontnote org.apache.commons.codec.**
-dontnote org.apache.http.**
-dontnote okhttp3.**
-dontnote org.kobjects.util.**
-dontnote org.xmlpull.v1.**
-keep class okhttp3.** {
      *;
 }

-keep class org.xmlpull.v1.XmlSerializer {
    *;
}
-keep class org.xmlpull.v1.XmlPullParser{
    *;
}
-dontwarn org.xmlpull.v1.XmlPullParser

-keep class org.xmlpull.v1.XmlSerializer {
    *;
}
-dontwarn org.xmlpull.v1.XmlSerializer

-keep class org.kobjects.** { *; }
-keep class org.ksoap2.** { *; }
-keep class okio.** { *; }
-keep class org.kxml2.** { *; }
-keep class org.xmlpull.** { *; }

score 0 · Answer 10 · edited Jun 20 '19 at 09:40

I got the same error message when I was trying to build release build in android after install react-native-firebase.

These are the steps I followed,

Do all the configurations they mention in the react-native-firebase documentation.
Build an android app using this command

./gradlew assembleRelease
Got this error message.

FAILURE: Build failed with an exception.

What went wrong: Execution failed for task ':app:transformClassesAndResourcesWithProguardForRelease'.

Job failed, see logs for details

Resolved this issue by changing this code line in android/app/build.gradle

minifyEnabled true

to this

minifyEnabled enableProguardInReleaseBuilds

This was the only change I did. It works for me.

score 0 · Answer 11 · answered Jul 03 '19 at 06:45

0

add -ignorewarnings in your proguard file and keep only those class that you did not want to obfuscate. Some of the libraries suggest to keep some of their classes if you are using proguard rules. Visit your libraries for details

answered Jul 03 '19 at 06:45

user3135923

61
1
6

score 0 · Answer 12 · answered Nov 25 '20 at 17:02

0

add this line to gradle properties

android.enableR8=true

answered Nov 25 '20 at 17:02

Ambesh Tiwari

648
7
11

Hi Ambesh. Thanks for your answer. Usually answers with an explanation are more welcomed there. Would you like to add an explanation to your answer? You may improve formatting of your answer as well. – MaxV Nov 25 '20 at 20:02

transformClassesAndResourcesWithProguardForRelease FAILED

12 Answers12

Linked