Geek Answers Handbook

Runtime exceptions are delayed using ACRA and not displayed on Logcat

I successfully implemented ACRA (Android Application Crash Report) in my project and error reports were sent to Google documents correctly. But ... when the exception occurs in my application, it does not appear on my logcat, and this is what I get:

ACRA caught a RuntimeException exception for com.my.project. Building report.

So, ACRA catches errors and prevents Logcat from showing what happened. I am currently developing my application and I do not have time to open Google documents for every problem. Should I disable ACRA for development and include it in production?

+6
source share
2 answers

Are you filtering the logarithm? In my applications, I see errors in logcat even with ACRA, but their level boils down to a warning, not an error.

Try decreasing LogCat filtering.

+2
source

You have something else in your application (or your IDE) that causes this behavior.

ACRA does not swallow any Exceptions. They will appear in your journal, as well as in your error repository (in your case, a Google document).

0
source

More articles:


All Articles