Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the best way to remove logging from production android application. It appears that proguard does not do this completely, strings still get written, so I was wondering what is best solution to remove the logging from production code?
The IMO best solution is to write code like below wherever you call your logging methods.
By changing 1 constant you strip away every logging that you don’t want. That way the part behind
if (false)should not even get into your .class file since the compiler can completely remove it (it is unreachable code).This also means that you can exclude whole code blocks from your release software if you wrap them in that
if. That’s something even proguard can’t do.the
SOME_LOG_CONSTANTcan beBuildConfig.DEBUGif you use SDK Tools r17 and above. That constant is automatically changed for you depending on build type. Thx @Christopher