Is there any way to upload exception logs thrown by Android to Server ?
Regards
Take a look at ACRA or BugSense.
You can view the brief report in "Exception/ANR" from Google Play Store
It is also suggested to use Google Analytics
It is very easy to use, and able to record all uncaught exception by setting a value to true in XML
Crittercism will do what you need without having to do it complex way. Just download the library, and integrate it.
It is easy to integrate, and much more reliable as compared to Google Play Store. Crittercism catches all exceptions, thread stack (so that u can check if there are any threads waiting doing nothing) and also the type of device. As compared to Play Store that just has a mention of about 1% of my crashes.
Google Analytics on the other hand is much more heavy as compared to flurry. I recommend a combination of flurry and crittercism.
If you don't want to use a third party lib, you can catch the exceptions yourself and do whatever you want with them like this -
UncaughtExceptionHandler currentHandler = Thread.getDefaultUncaughtExceptionHandler();
// Register if not already registered
if (!(currentHandler instanceof ExceptionHandler)) {
Thread.setDefaultUncaughtExceptionHandler(new ExceptionHandler(this, currentHandler));
}
Do this in the Application class.
In Android, Google officially supporting Fabrics's crashlytics online tool with Firebase for managing crash related informations. Also we can upload any exception to the server.
Also they provide a dashboard for visualizing many things related to our app.
Related
In my app ,i have integrated Crashlytics ,ACRA and Google Analytics for reporting crashes
-> is there any side effect of one on others ?
-> Which one is better to use.
-> How crash reporting tools work ,if one caught the crash how other will get to report the same crash ?
Using multiple crash reporting solutions in one project simultaneously might run your application into concurrency issue, where application eventually hangs forever upon any crash.
Crash reporting solutions intercept uncaught crashes, in one way or another. The flow is basically the same:
Intercept uncaught crash;
Log it to be able to send info to server;
Re-throw crash, so that the app eventually crashes.
I could imagine a situation where 2 crash reporting solutions create an infinite loop throwing the same exception to each other forever, according to the steps above.
At least, that's what it looked like when I used Google Analytics (with crash reporting turned on) together with Crashlytics. The application just hanged forever without any visible crashing, until I eventually turned Google Analytics crash reporting off.
is there any side effect of one on others ?
Google Analytics is not really good to use. I created a Google Analytics account a few days before the implementation. It had not been used and not even been copied(the code) and when I came back to insert Google Analytics I had to get the code. Noone had used a Google Analytics version of the app and it wasn't even released and it had a lot of usages logged. I don't like google analytics because the code's are easy to crack and are used by third party websites without consent to add fake clicks on your website when the code isn't even used there.
Additonally, Google Analytics does only handle when it is forced to log. As it is not a dedicated crash analytics tool it does not log crashes like ACRA, Crashalytics and Firebase crashes.
Which one is better to use.
That is really up to you, but personally I find ACRA to be better because you can use backends on your own site. If the site goes down, so does ACRA so it really helps to feel in control of the bringing the site back up.
Additionally, there are many backends if you want to use your own site. And if you don't find one that works you can create one. Crashalytics and Firebase rely on their own dashboard on their respective pages, which means another password and username to remember.
How crash reporting tools work ,if one caught the crash how other will get to report the same crash ?
See Drew's answer
Crash analytics tools Might be using Global Exception handling as in this https://stackoverflow.com/a/8877177/1602333 for entire App to handle uncaught Exceptions.
SO if you use multiple crash analytics tools , each of them may replace Global Exception handler .
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 would like to catch Exceptions and also track how the program runs, also interaction of user...
Can anyone give me some directions?
I need to implement Logging in my Application.
Check out the following:
Google Analytics for Android:
https://developers.google.com/analytics/devguides/collection/android/
Crittercism for bug tracking like you are describing:
http://www.crittercism.com/
There are other bug tracking platforms but I only have experience with Crittercism.
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.
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.