Geek Answers Handbook

How to improve the quality of debugging data when my application crashes in the wild?

I had my first NullPointerExceptions in my application and it appeared in the developer console.

While I was starting to ask for advice here, I realized what the problem was, but it led to something that bothered me for a while - how to make it as easy as possible to debug my code when the only thing I have to access is the developer console and the stack traces present there.

In other words, is there anything I can do as a developer to improve the feedback I get when my application crashes into the wild? Maybe it's Google Analytics, maybe Instrumentation classes, but should there be a better way to get more context to help me debug my application when I don't have access to the user or his device for debugging?

+6
android remote-debugging
source share
2 answers

You can also use ACRA http://code.google.com/p/acra/

+4
source share

If you have enabled application logging, you can also send these logs using http://code.google.com/p/android-remote-stacktrace/ . This will give you an invaluable context on what the user actually did in the period before the failure occurred.

+1
source share

More articles:


All Articles