In the Google Play Developers Console, developers can see the crash reports of their App collected from end users. Is there any Apps public their crash reports?
I want to have an investigation of Android crashes, to see if there are some genera reasons. (in a large scale, thus I need crash reports from many Apps)
I am wondering is there any Open Source Android project which public their crash reports?
Yes you can but it depends on the developer weather he has used these kind of android libs to detect crashes.
For example
you are using some application it gets crashed.
you see a popup to submit that crash you send email.
in that email you can see that crash otherwise there are no such apps available as far as I know.
Related
I'm developing an Android app that is currently in the Play Store. I've been getting reports of a crash on certain devices that I can't reproduce, and the Play Store's built in crash diagnostics don't contain enough information. What I really need is the Logcat information from these devices, but it seems that Android 4.1 and above don't allow the use of those "Log Collector" apps that used to be so popular for this purpose due to security concerns. Is there a library that I can add to my app that will allow it to log to a remote server on demand? I know enough about this crash that I could put a call to some mythical sendLogcatNow() function in the appropriate spot in the code, if I had such a function. Since the information I seek is not actually part of the crash (the crash occurs later), normal crash reporting tools such as Crashlytics don't seem like they will do what I need, but perhaps they have this feature and it's just not prominent in the documentation. Thanks!
There are few version for crash reporting..
Hockey App
Acra
BugSense
Android Remote stack trace
Since your app can always read logs for it's own process, you can also implement something of your own.
Out of all these, I personally prefer Acra. as it is most efficient and give many options to app developers.
I'm using ACRA for logging crashes from my app but based on their documentation,
you can add your own variables content or debug traces to the reports
you can send error reports even if the application doesn't crash
Which seems to be doing what you want.
https://github.com/ACRA/acra
You will need to run your own ACRA server (simple enough to run) and get your app to send the crash logs to your server. Everything is detailed on their website.
I would look into using a third party production crash system, there are a few out there. I am currently using Crashlytics. This specific service allows you to log and set key value pairs during the running of the application that get packaged with the crash report. These services also offer greater insight into the device type, OS and a variety of other device details.
With this set up I have then created a log function that will submit to the Crashlytics service as well as logging it to log cat.
You can also use Google Analytics or Flurry. But note that Google Analytics doesn't log stack traces and Flurry doesn't support real-time log reports on server.
I just recently launched an application on the Google Play Store, and I was exploring the developer console and saw the tab for Crashes and ANR.
What does ANR stand for?
Also, my app seems to have crashed on some of my friend's phone before, but there was no way for them to "report" such crashes. How should I enable such functions for users to report crashes for me to see in the developer console under the Crashes/ANR tab?
ANR stands for Application Not Responding. If your app is doing a lot of work on the UI thread then you'll see one of those force close/wait dialogs. That's ANR.
As for crash reporting, if your app is distributed through Google Play then crash reporting is built in. When your app crashes, the user will get a dialog with the options "Force Close" or "Report." The user has to press the Report option to send you the crash report, otherwise you may never know.
If you're not distributing through Google Play, you might want to consider a library like ACRA which will email you crash reports, upload them to a Google Docs spreadsheet, or you can write your own custom handler for dealing with crash reports.
Details about ACRA can be found here: http://code.google.com/p/acra/
Below is a sampling of what these dialogs look like. Close/report dialogs on the left and ANR on the right. Android 3.0+ is on top with the older dialogs on the bottom.
When an application crashes, a tombstone is generated. Essentially, your app needs to be aware that portions of it crashed (if you rely on some API or library that provides callbacks / status) but if it's really just your app dying - you will have a somewhat hard time figuring out whether it crashed or not.
"Error reporting" isn't a premade class you can use in android, and you may have to roll one of your own. Then again, there's ACRA - http://acra.ch/
some links:
http://android-developers.blogspot.com/2010/05/google-feedback-for-android.html
http://developer.android.com/distribute/googleplay/strategies/app-quality.html
To collect crash reports as a developer one uses logcat. Is there a standard way for a published android application to capture crash logs so that your users can send them to you?
Is there any callback that is called when an app crashes for example? Can the strategy that logcat uses to log be adopted to a production game?
Similar question for iOS Apps:
How can I allow users to give me feedback and submit bug reports for my iOS app?
Related Question
How can I accept bug reports and other user feedback from within my app?
EDIT 1:
In addition to the frameworks mentioned in the answers below a lower level approach to capturing all uncaught exceptions can be used an is mentioned here Ideal way to set global uncaught exception Handler in Android
I personally use ACRA. I found it easy to integrate, and it meets my requirements.
Reports are sent to a spreadsheet in Google Docs, and it can be configured to send you an email every time the app crashes
Using logcat is a solution but is only feasible when crashes are coming from your own device. However, you can have the crashes occurring on your users’ devices automatically sent to you as well, including all crash and device details.
This could be done through Instabug which is a bug & crash reporting service.
It automatically sends a report containing all crash and device details once a crash occurs, plus It only takes a line of code to integrate in your app.
For full disclosure, I work at Instabug. Let me know if I can help.
You can include Flurry Analytics in your app, which does create an error log when something craches and sends in back to the server, which you have access to. It will give you all the information like the LogCat.
I hope this helps.
There is also FirebaseCrash by Google which reports logs on your Firebase console.
Read more about it here
The Google Play Developer Console also reports crashes and application not responsive, under crashes and ANRs for each app.
I was just using Sports Tracker when it crashed, and when I pressed "Report" button to report the crash, I'm given a simple input field asking for a comment regarding the crash.
However, pressing "preview" will give me insight of what data is being send with the crash log. The amount of data is actually immense, including date/time, device name/version, system log, stack trace etc. All kinds of usable data.
From logcat I can see that this is com.google.android.feedback activity.
The question is, is this something Sports Tracker developers implemented themselves, or is it the default crash report every android user has installed on their phones? In other words, do all my apps (=the ones I've written and posted to Play Store) already have this function, or is it something I could/should implement myself**?
I have received some crash reports via android's build in crash reporting service, but it doesn't really give me any useful data (besides stack trace). Or is it just that the crash reporting on developer's dashboard is still far from complete?
I don't know about this special feedback activity. I'm currently using the ACRA system that it's really easy to use and give me useful bug reports. Let's have a look on it for your bug report.
I am sure they must be using one of these.
ACRA is great as well as try ZUbhium, it comes with silent crash reporting & in app support desk. So whenever application crashes, it captures more meaningful data and does analysis onit .
You can either add Zubhium as backend to ACRA & view advanced crash reports or use ZubhiumSDK. Both do excellent job.
Actually TestPoke is a beta testing platform that allow you to see all crashes your android app fall in, even thought they notify you when such thing happens through it Android App.
http://www.testpoke.com
We are converting out suite of iPhone apps written in .NEt MonoTouch to Android.
How do we catch, then publish exceptions so that they are reported via the Android Market?
You should also try Bugsense.com, it's free and allows you to track exceptions in Android.
PS: I am the founder
You need to use:
Thread.setDefaultUncaughtExceptionHandler(handler)
There you can catch everything and send mails, notifications, etc.
EDIT:
Check this questions, are basically the same:
Global uncaught exception handler -> email log to me?
is it possible to replace the default “Force Close” dialog in Android?
I highly recommend using the library android-remote-stacktrace. It uses the methods Macarse mentions but wraps it in a useful POST to your server, which you can use to put into a database or send an email.
You could also try Android-Error-Reporter which POSTs unhandled (or if necessary handled exceptions as well) to your server similar to android-remote-stacktrace but more reliable and it allows you to ask the user before sending the error report.
There's also Google's ACRA project (Application Crash Report for Android).
ACRA is a library enabling Android Application to automatically post their crash reports to a GoogleDoc form. It is targetted to android applications developers to help them get data from their applications when they crash or behave erroneously.
A few points about ACRA that are relevant to this question:
more detailed crash reports about the device running the app than what is displayed in the Android Market developer console error reports
you can add your own variables content or debug traces to the reports
you can send error reports even if the application doesn't crash
We recently started using ACRA in Andromo to receive crash reports, since the apps made with Andromo are uploaded to the market by the user who designed the app, and not by us. (Otherwise we'd rely on our users to forward any crash reports to us.)
That it also sends reports for apps that haven't been uploaded to the market is a nice bonus, because we could potentially catch problems while an app is still being tested, before the user uploads it to the market.