Home/ Questions/Q 8617909
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-12T05:58:58+00:00

In my Android application I utilize setDefaultUncaughtExceptionHandler to store information about unhandled exceptions locally

  • 0

In my Android application I utilize setDefaultUncaughtExceptionHandler to store information about unhandled exceptions locally on a user device. After some feedback I suspect that this code prevents the built-in Google’s error-reporting feature from work, because I do not see error reports in the developer console, while exceptions are reported by users. Their devices are well past 2.2, where the error-reporting was introduced. Could it be that specific device with, say, 4.0.3 does not support this feature? If yes, how can I detect this programmatically?

I can’t find information regarding this in Android documentation. I’d like both standard error-reporting and my custom handling work together. In my custom exception handler I call Thread.getDefaultUncaughtExceptionHandler() to get default handler, and in my implementation of uncaughtException I propagate exception to this default handler as well.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Yes, this will stop the inbuilt error report. The user is given a dialog when your app crashes, with an option to report the error via Google Play. However, if you use setDefaultUncaughtExceptionHandler() then the exception is handled within your app, and no option is given to report it.

    I recommend that you integrate ACRA into your project, as it allows you to easily receive error reports upon crashes.

    • 0