Home » Android » Android crash reporting library (pre Froyo)

Android crash reporting library (pre Froyo)

Posted by: admin April 23, 2020 Leave a comment

Questions:

Do you know any crash reporting library for Android?

I don’t want to spend a lot of time to write my own reporting system.
The output can be send to the email or some kind of server.

I know that Google introduced crash reporting in Froyo, but I want something for older versions of the system.


Let’s sum up the answers:

How to&Answers:

This is what you are looking for: android-remote-stacktrace
It sends an email / calls a php script when your application crashes and sends the logcat output. Quite simple to use and very useful!

Remotely log unhandled exceptions in your Android applications

Answer:

You can also try out a service done by my company just for that purpose (and a bit more) http://apphance.com . It allows not only to get crashes, but also logs, screenshots whenever tester reports a problem. It reports it to the cloud and lets developer to browse through the sessions/logs/crashes/issue reports using a useful web panel.

It is more targeted for testing part, but soon there will also be a production-version available. It is also cross-platform – not only Android but also iOS and soon more.

Disclaimer: I am CTO of Polidea, company behind Apphance, co-creator of the app.

Answer:

You can also try BugSense. BugSense collects and analyzes all crash reports and gives you meaningful and visual reports. It’s free, used by big applications (with more than 10.000.000 users) and it’s only 1 line of code in order to integrate.

Disclaimer: I am a co-founder

Answer:

I wrote an Error-Reporting Library for my own project which is very easy to integrate. It allows you to send error reports to a http server (similar to android-remote-stacktrace). It’s open source and can be downloaded from github: https://github.com/tomquist/Android-Error-Reporter

Answer:

Android is all open source, so perhaps you could just extract that part of Froyo and add it to your app as though it were a third-party library. I don’t know how easy or feasible that would be, but if it works for you, let us know!

http://source.android.com/source/download.html