CODEWITHSUNDEEP
androidproguard
Leem.fin
Leem.fin

Reputation: 42582

My log messages are not removed with proguard configuration

I am developing my Android app.

Then I enable & configure proguard by:

Step 1. Enable proguard:

In project.properties I have:

proguard.config=${sdk.dir}/tools/proguard/proguard-android-optimize.txt:proguard-project.txt

I also tried the following:

# To enable ProGuard to shrink and obfuscate your code, uncomment this (available properties: sdk.dir, user.home):
proguard.config=proguard.cfg

Step 2. Configure proguard:

In proguard.cfg I have:

-assumenosideeffects class android.util.Log { *; }

I think the above configuration should remove all logs.

But when I install the APK under target/ folder & run my app, I can still see all my Log messages in logcat console. Why?

Upvotes: 7

Views: 3473

Answers (3)

Lavekush
Lavekush

Reputation: 6166

You can create your own Log utilit class and use it,

What I do when I release my apps is: I create my own Log class with methods i, d, e, w etc and use this Log class instead of the Android one, because then I can use a simple switch like boolean debug = true according to which I write to the LogCat or don't. That way I can leave all my log statements in the app. When you've written your own Log class, to use it all over your app, you can simply replace all,

Remove: 

import android.util.Log;

Add

import your.package.Log;

Like this:

    public class Log {

        public static void i(String logTag, String logString) {

            if (isLogsEnabled) {
                Log.i(logTag, logString);
             }
        }

        public static void v(String logTag, String logString) {

            if (isLogsEnabled) {
                Log.v(logTag, logString);
             }
        }

          // you can add method for w,d,wtf also...
    }

Logging is a very handy debugging and diagnostic technique used by developers. Use the logging class provided as part of the Android SDK to log important information about your application to LogCat, but make sure you review your application’s logging implementation prior to publication, as logging has performance drawbacks.

Before releasing your application Review your log carefully so its doesn't leek any confidential data,

Log is very important whenever your application in testing mode, Logs will provide you current state and scenario of your application on current device. So its very helpful whenever you will update your application.

Sometime Google play reject your application if they was found your Logging mechanism violate the rules.

Upvotes: 0

Eric Lafortune
Eric Lafortune

Reputation: 45648

You should use the first line in your project.properties:

proguard.config=${sdk.dir}/tools/proguard/proguard-android-optimize.txt:proguard-project.txt

You should then add these lines to your proguard-project.txt (not the deprecated proguard.cfg):

-assumenosideeffects class android.util.Log {
    public static boolean isLoggable(java.lang.String, int);
    public static int v(...);
    public static int i(...);
    public static int w(...);
    public static int d(...);
    public static int e(...);
}

These options only have any effect if the file does not contain -dontoptimize.

Ant and Eclipse pick up the settings from project.properties. Gradle and Maven require equivalent settings that specify the configuration files, in build.gradle and in pom.xml respectively.

Similar questions and answers:

Upvotes: 11

NickT
NickT

Reputation: 23873

I can't remember where I found the reference to this method, but I've always used this:

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

in my configuration. It does remove debug and verbose logging that I wrote

Upvotes: 1

Related Questions