optimization - Removing logging with Proguard and optimized Android config file -


my proguard config file uses following remove log statements:

-assumenosideeffects class android.util.log {     public static *** d(...);     public static *** e(...); } 

apparently takes effect when optimizations turned on, reference proguard-android-optimize.txt in project properties file, instead of proguard-android.txt.

is inconsequential change make? proguard-android-optimize.txt says "adding optimization introduces risks, since example not optimizations performed proguard works on versions of dalvik" mean, , can possibly not use proguard-android-optimize.txt , instead add optimization statements necessary own config file log removal takes effect?

thanks. total proguard novice.

you can indeed remove logging if optimization enabled.

optimization should pretty stable in current versions of proguard. can replace <android.sdk>/tools/proguard/lib/proguard.jar latest version if wish. instance, version 4.9 has improvements remove traces of logging code, compared version 4.7 in android sdk @ time of writing (indicated output of "java -jar proguard.jar").


Comments

Popular posts from this blog

php - Calling a template part from a post -

Firefox SVG shape not printing when it has stroke -

How to mention the localhost in android -