Closed GoogleCodeExporter closed 9 years ago
One possible workaround is to replace the default uncaught exception handler
right before ACRA gets initialized in your Application-derived class:
Thread.setDefaultUncaughtExceptionHandler(sUncaughtExceptionHandler);
ACRA.init(this);
And then define:
private static UncaughtExceptionHandler sUncaughtExceptionHandler = new
UncaughtExceptionHandler() {
@Override
public void uncaughtException(Thread thread, Throwable ex) {
android.os.Process.killProcess(android.os.Process.myPid());
System.exit(10);
}
};
Original comment by npeer2...@gmail.com
on 9 Nov 2011 at 6:48
I don't think it is a good idea to simply restart the application. Your user
was doing something, it did not work as expected and he certainly will see some
awkward behavior from your app. You would better consider using the TOAST mode
instead to let your users know that something went wrong without displaying the
hated Force Close dialog.
Kevin
Original comment by kevin.gaudin
on 2 Jan 2012 at 9:44
Original issue reported on code.google.com by
npeer2...@gmail.com
on 8 Sep 2011 at 5:20