ACRA remove certain type of errors

[Dragos Ivanov]

Hi,

Is it possible to remove certain type of errors from the reports? For example Connection type ones?

Thank you 

[William Ferguson]

Sure. Catch them and handle them within your app.

[Dragos Ivanov]

Hi,

I`m not saying about catching and handling errors inside the app. I`m talking about the ACRA reports. For example the app is sending now a report like this

customReportContent = {
        ReportField.REPORT_ID,
        ReportField.APP_VERSION_CODE,
        ReportField.APP_VERSION_NAME,
        ReportField.PACKAGE_NAME,
        ReportField.ANDROID_VERSION,
        ReportField.PHONE_MODEL,
        ReportField.BRAND,
        ReportField.CUSTOM_DATA,
        ReportField.USER_APP_START_DATE,
        ReportField.USER_CRASH_DATE,
        ReportField.STACK_TRACE,
        ReportField.LOGCAT,
        ReportField.EVENTSLOG,
        ReportField.RADIOLOG,
        ReportField.DEVICE_ID,
        ReportField.INSTALLATION_ID,
        ReportField.ENVIRONMENT,
        ReportField.AVAILABLE_MEM_SIZE,
        ReportField.TOTAL_MEM_SIZE

}

That means that is sending all the errors. I want to make it stop sending all and send just a few of them. 

[William Ferguson]

ACRA has no in built mechanism to do this because ACRA was designed to report all application crashes.

You are trying to get it to not report some application crashes.

You could replace ACRA's UncaughtExceptionHandler with your own that then delegates to ACRAs if you want a crash to be reported.

What is an example stacktrace of one of these crashes that you want to ignore?

William

--
You received this message because you are subscribed to a topic in the Google Groups "acra-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/acra-discuss/cdMIH8QWAAo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to acra-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[F43nd1r]

If you want to exclude certain Execptions, that means you know where and why these exceptions occur and have chosen to ignore that error. In this case you should catch the exception as close as possible to the location where they occur to document that these exceptions are knowingly ignored in that specfic code block. ImO allowing filters on reported exceptions would promote bad style, as it would be pretty hard to understand why an excpetion type was previously filtered (because the filter is not linked to the crashing code at all). This could also suppress important exceptions because they share a type with an ignored exception.

[Dragos Ivanov]

I do not have an example, but I would like to ignore all Connection type exceptions.