Android Studio & ProGuard: cannot resolve symbol getDefaultProguardFile?

Question

IDE: Android Studio 1.1.0

Subject: ProGuard

Problem: ProGuard files or tools not recognized by Android Studio, getDefaultProguardFile can not be resolved and there's no proguard-android.txt and proguard-rules.txt files in the app, see the image below: (from build.gradle)

build.gradle screenshot

How to fix this and achieve ProGuard protection to my App ?

Hi. It seems like the default filename generated by Android Studio is proguard-rules.pro. The one showing in your gradle file is proguard-rules.txt. It could just be the filename. — Christian Abella, Apr 09 '15 at 00:44
Try rebuilding your project, then sync the project with the gradle files. — Mounir Elfassi, Apr 09 '15 at 09:39
I'm using Android Studio 1.5.1. In my case works like a charm. Please could you post your *dependencies {...}*? — Susanna Martinelli, Feb 18 '16 at 15:50
Cutting and pasting the code from and back to the same location eliminated the error warning for me. I had same issue/fix for 'signingConfigs'. It never prevented me from compiling, so maybe it was a false positive, at least in my case. — Androidcoder, Jul 26 '16 at 15:14

score 8 · Answer 1 · answered Jan 06 '16 at 12:26

I had the same trouble as shown here:

The error message makes it seem as if the file is not being found, and therefore not read. However, I went to into sdk/tools/proguard folder to find the file, and at the top added a statement to test if the file was actually being read. I put at the top "Will this crash it?"

As you can see from the error, the file was indeed found during the build process and the statement I added crashed it. Thus, it appears the "can't resolve symbol" error is giving a false positive.

score 7 · Accepted Answer · answered Apr 09 '15 at 09:16

7

Try to change into -

proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

answered Apr 09 '15 at 09:16

Amit K. Saha

5,871
2
27
35

I did, it's not working actually `Android Studio` not recognizing the method `getDefaultProguardFile` – Fadi Obaji Apr 09 '15 at 09:20
1

@FadiObaji do you have "proguard-rules.pro" file under app folder? – Amit K. Saha Apr 09 '15 at 09:22
make sure you have this line at the top of your gradle file" apply plugin: 'com.android.application'" – Amit K. Saha Apr 09 '15 at 09:31
1

Yes it's there, still no luck, i think if i deleted the `tools` folder from the sdk folder and then re-download it will fix the problem, because i copied the entire `SDK` folder from another windows – Fadi Obaji Apr 09 '15 at 09:48
could be a cause. Best of luck at your journey :| – Amit K. Saha Apr 09 '15 at 09:49
Have you guys found any solution to this? I've wasted 2 days for searching and figuring out solution for this. – lightsaber Nov 08 '15 at 17:55

Martin Pfeffer · Answer 3 · 2015-04-20T10:59:05.347

4

I really had the same issue. So here is what made my project working:

release {
    minifyEnabled true
    proguardFile 'proguard-rules.pro'
}

Tested by this code:

 Log.d(TAG, "TEST!");
 Log.i(TAG, "INFO!");
 Log.e(TAG, "ERROR!");

In proguard.pro I placed this snippet (which removes all Log.d-Statements in the byte-code)

-assumenosideeffects class android.util.Log {
    public static int d(...);
}

And the cat says:

MainAct﹕ INFO!
MainAct﹕ ERROR!

-> exactly what I tried to achieve :)

PS: This assumes that you have the proguard.pro file in the module (aka 'app') folder.

edited Apr 20 '15 at 10:59

answered Apr 20 '15 at 10:49

Martin Pfeffer

12,471
9
59
68

Actually when i made a `signed apk` everything worked fine and i de-compiled the file to see if `proguard` worked and it did work, i don't know why `android studio` says `can not resolve symbol` – Fadi Obaji Apr 20 '15 at 12:52
Ohh, nice. In my situation (hiding the Logs), AS will only run the proguard config if I set the file as I wrote it above. – Martin Pfeffer Apr 20 '15 at 12:55
i think `proguard` removes all `logs` from your apps without telling it to do so, it's in the `proguard` description – Fadi Obaji Apr 20 '15 at 12:57
this shouldn't be the default-behavior.. (AFAIK)^^ – Martin Pfeffer Apr 20 '15 at 13:01
What about the other methods something like `options.compilerArgs` ? also i have `cannot resolve symbol options` – Ibrahim Disouki Nov 02 '15 at 06:59

score 1 · Answer 4 · answered Jul 25 '16 at 16:58

1

Try:

proguardFiles.add(file('proguard-android.txt')) proguardFiles.add(file('proguard-rules.txt'))

This structure works in the gradle-experimental plugin.

answered Jul 25 '16 at 16:58

IgorGanapolsky

26,189
23
116
147

score 0 · Answer 5 · answered Aug 21 '16 at 14:52

I fixed the issue of Android Studio not recognising the method by using double quotes instead of the single. The below is what I ended up using:

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

score -1 · Answer 6 · edited Sep 01 '16 at 12:06

-1

try this,

{
  minifyEnabled false
  // proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' 
  proguardFiles 'proguard-rules.pro'
}

edited Sep 01 '16 at 12:06

V-rund Puro-hit

5,518
9
31
50

answered Sep 01 '16 at 11:42

Suman Dev

1
1

score -7 · Answer 7 · answered May 14 '15 at 05:48

-7

In my case:

buildTypes {
    release {
        runProguard false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}

replace runProguard false with minifyEnabled false works.

answered May 14 '15 at 05:48

Omama

147
1
2
9

3

`minifyEnabled false` will disable ProGuard obfuscation – Roman Sep 16 '15 at 11:27

Android Studio & ProGuard: cannot resolve symbol getDefaultProguardFile?

7 Answers7

Linked