I'm using the Google Analytics v4 API on an Android app that was built with proguard. The resulting crash reports are cryptic. For instance, `NullPointerException (@a:t:-1) {main}'
1) Can I find the exact location of this crash with the information provided without guessing?
2) How can I improve the readability of the crash reports? The documentation shows how to set a custom exception reporter and that makes sense. However, it also states
Never send the exception message (e.getMessage()) to Google Analytics as it may contain personally identifiable information.
So if not the message, what fields of the exception could I use to generate a crash report that lets me find the position of the crash on an app with proguard?
The solution is to override StandardExceptionParser to also report the package name of the root cause. See my blog post for a way more detailed description.