ACRA currently logs the stack trace of an exception but not the detailed
message.
The message can be very useful when resolving certain bugs, such as those that
occur in the framework's code.
In the meantime, I'll be using putCustomData() to log this information, but it
would be nice if this was standardized in ACRA as a new dedicated column next
to the stack trace.
Original issue reported on code.google.com by npeer2...@gmail.com on 8 Mar 2012 at 9:39
Original issue reported on code.google.com by
npeer2...@gmail.com
on 8 Mar 2012 at 9:39