Should I remove e.printStackTrace() from my code before publishing

I was reading the the Android Publishing docs and they said to remove all Log calls from my code. I have some calls to e.printStackTrace() in my code that can be printed as part of the normal running of my program (ie. if a file does not exist yet).

Should I also remove these calls?

Asked by: Carlos386 | Posted: 20-01-2022

Answer 1

You shouldn't be using e.printStackTrace() directly anyway — doing so will send the info to the Android log without displaying which application (log tag) it came from.

As others have mentioned, continue to catch the Exception in question, but use one of the android.util.Log methods to do the logging. You could log only the message, but not the stack trace, or use verbose logging for the stack trace:

try {
    Object foo = null;
} catch (NullPointerException ex) {
    Log.w(LOG_TAG, "Foo didn't work: "+ ex.getMessage());
    Log.d(LOG_TAG, Util.stackTraceWriter(ex));

You should strip DEBUG or VERBOSE log messages from your production builds. The easiest way is to use ProGuard to remove Log.[dv] calls from your code.

Answered by: Fiona617 | Posted: 21-02-2022

Answer 2

If you allow an Exception to propagate up to the OS then the OS will log it and also pop up a Force Close window, killing your application. If you catch it, then you can prevent your application from being force closed.

If you want your users to have the ability to send you errors that they are getting, then I would log the stack trace. They can then send you the log via an app like Log Collector.

If you want to avoid the possibility of exposing your stack trace information to your users, then catch the exception and don't log it.

Answered by: Alberta366 | Posted: 21-02-2022

Answer 3

I would use Log class for message out put. For logs that you think are important to stay in the app - use Log.i for errors warning - Log.e Log.w For you debug Log.d - and that you can turnoff on base on if your application is in debug mode.

Answered by: Joyce253 | Posted: 21-02-2022

Answer 4

Well printStackTrace() will log it into the OS, causing your andorid (or computer) app to terminate (force close), instead, do something like this:

public void nullPointerExceptionCauser()
           Object example = null;
      catch (Exception e)
           Logger.log(Level.SEVERE, "Caught Exception: {0}", e.getStackTrace());

Answered by: Miller190 | Posted: 21-02-2022

Answer 5

in my modest opinion (I'm not an Android developer)

It should be nice. I don't know the logging options for Android but I'm sure you have some configurable thing to output (or not) your traces.

And if you don't do printStackTrace() Android will not be doing the dirty work of ignoring it.


It's only a good-feeling (style) thing.

Answered by: Dainton227 | Posted: 21-02-2022

Answer 6

If you want to be secure i.e. not allow anyone snooping to read exception logs you can do something like

private void hideExceptionsInReleaseMode()
    final Thread.UncaughtExceptionHandler defaultHandler = Thread.getDefaultUncaughtExceptionHandler();

        Thread.setDefaultUncaughtExceptionHandler(new Thread.UncaughtExceptionHandler()
              public void uncaughtException(Thread thread, Throwable ex)
                  defaultHandler.uncaughtException(thread, new RuntimeException("Something went wrong :p"));

Answered by: Julian601 | Posted: 21-02-2022

Answer 7

In order to use printStackTrace in a safer way I would use StringWrite and PrintWriter:

catch (final Exception e)
   final StringWriter sw = new StringWriter();
   final PrintWriter pw = new PrintWriter(sw);
   Log.e("TAG", sw.toString());

Or alternatively:

 catch (final Exception e)
    Log.e(TAG, Log.getStackTraceString(e));

Answered by: Dominik681 | Posted: 21-02-2022

Answer 8

Use this to remove the logs from release apk

if (BuildConfig.DEBUG) Log.d(TAG, "your meseage");

Answered by: Sydney621 | Posted: 21-02-2022

Similar questions

java - Confusion with e.printStackTrace() in Android

I read here that e.printStackTrace() should not be used to catch exceptions on android. On another source I read that I should use Log.e() instead of e.printStackTrace(): ... catch (Exception e) { Log.e(TAG, "Foo did not work", ...

Still can't find your answer? Check out these communities...

Android Google Support | Android Community | Android Community (Facebook) | Android