I have an App available in the Android Market.
From time to time i get error reports in the Developer Console. For about 6 month there have been no more stack-traces visible. At first I though no more post-froyo bugs: 'yay'!
Recently I did some testing using a droid 2 which I am sure is not pre-froyo, I ran into an error, reported it, and never received this report in the Console.
Did I miss some configuration or option that enables me to receive stacktraces?
Is there something I can do about it?
I have no idea why you don't receive stack traces anymore nor how could you enable them. I have always felt Android Market is a somewhat unreliable service: reports are not accurate, downloads/active counts randomly change at times, crash reports not received, and so on.
However, I have suggestions how to implement similar functionality yourself and with a more reliable fashion: How do I obtain crash-data from my Android application?
Basically there are two options:
Use an existing component (like acra)
DIY by catching all uncaught exceptions.
(So you would have an option should you fail to receive a real solution)
I'd suggest you to stop listening to android market and work with other tools.
You should consider using a crash report tool like http://www.bugsense.com/ which is simple effective and meaningful
NOTE: i am not linked nor affiliated in any way with bugsense owners. I am just a simple user.
Related
I want to add a Bug Report/Report Problem option to my app, which sends device and app info and a user's comment to the developer. I was wondering if there are any "standard" things to report? I am reporting OS Version, Device Name and App Version. Is there anything important I'm missing out and should include? What are you guys normally including ?
You could avoid sending out this data manually by integrating with a service like Instabug
which allows the user to report bugs through your preferred method, but mainly through shaking the device.
It will display a screenshot of the current view that the user can draw on for visual bug identification. What gets reported along is (but not only) the following:
App version
Device type
OS version
Location
CPU load
Memory usage
Storage
Connectivity
Battery
Orientation
Network and console logs
Visual reproduction steps
UI view hierarchy inspection
users can further describe the bug using text, extra screenshots, voice notes, or screen recordings.
All reports arrive in your Instabug dashboard containing various details such as:
Network and console logs
Complete Device details
Reproduction steps
Crash stack trace (In case of a crash report)
It only takes a line of code to integrate.
For full disclosure, I work at Instabug. Let me know if I can help.
Check out the free service
http://www.crashlytics.com/
you can get the features what is mentioned above.
I hope title itself says what my question is.
My app is crashing at very rare scenarios like nearly 1 out of 100 times.
I am not using any crash log tools and not logging exception causes.
I want to know does Android system maintains any crash log report when the app is crashed either in System level or in App level.
Thanks
Android system maintains a crash report and sends to the developer but the user has to allow this.
And then you can check it here in Android Developer Console:
As an alternative you can use third-party loggers like Liquid, Crashlytics (mention in another answer), Splunk MINT Express (ex-Bugsense) or any other from this links
I don't think so, if you can't debug it in real time with the IDE (DDMS and LogCat), you must use Crashlytics or any other similar tool.
I use it in all my apps, it is very useful.
When we published our Android app we decided to use Airbrake as a 3rd party exception reporting service. I integrated the loopj Airbrake notifier (https://github.com/loopj/airbrake-android) into our app and it seemed to be doing fairly well.
Over the past two weeks we have seen an explosion in downloads and as a result an increase in exceptions being reported. I was getting some really weird exceptions so I decided to look at the Android Developer Console for the application in Google Play. The interesting thing I found was that the number of errors in the Google Play dashboard was less than 10% of the total number I have in Airbrake. Then I decided to double check with Flurry. The number of exceptions that Flurry seems to have encountered is similar to what Airbrake is showing me, which leads me to believe that Flurry gathers these stats in the same way as Airbrake.
So what I want to know and cannot find any good answers to:
What is Google / Android doing differently than a normal uncaught exception handler?
Should I just throw Airbrake out and use the Google Play error reporting only? (Our app does go back to 2.1, but we can live with that)
What is Google / Android doing differently than a normal uncaught exception handler?
Among other things, they only log the exception to the server if the user clicks the "Report..." button, AFAIK. Since many users will not do that, you will get a subset of the actual exceptions that occur.
since the latest version of my Android application I got some bug reports (via email) that my application doesn't work anymore. It does not crash but doesn't work anymore. Only a few users (<0.05%) have this problem. I don't see any similarities (same phone/provider/...).
Has anyone an idea how I can tackle this problem and find the bug?
If I publish a debug version of the application, is there any tool that the end-user can use to grab the logcat output and send it per email or...
Thanks!
My suggestion is that you incorporate a logging feature on your app, even the retail one. Make a log of critical/fatal errors, but try to minimize the log size (e.g. erasing it periodically or only logging really really critical errors). This way you can request such logs for such users, without having them install a new version of the app, and having them to recreate the erros, since sometimes recreating the whole situation in which such crashes occur is close to impossible, or that it doesn't happen for some other reason in a debug version.
You can also incorporate a function that sends you the log periodically, or just request it to the users.
I don't know any tool other than ADK to grab the logcat...
One of the best debugging tool available is the ACRA library.
Below are few links, which will help you to use this library.
1) http://code.google.com/p/acra/downloads/detail?name=acra-4.2.3.zip&can=2&q=
2)http://code.google.com/p/acra/wiki/BasicSetup
Let me know if you are stuck somewhere.
I posted a free app and I've got a couple users who posted a comment saying that the app force closes in google's feedback. It's got a few hundred downloads in the day it's been up with an 84% retention rate. Google's error report in the developer's console says it has 0 errors. I've never had an app that reported any errors in the console. Does it actually work or am I getting fake reports of force closes? I'm a bit suspicious competitors might be posting the comments, but I don't have any way to confirm that the error reporting google provides does actually work.
As far as I know, the 'Report' button is only available on devices running FroYo (2.2) or later, which is very few.
At least I've never seen the ability to report an error upon force close.
I don't think there's any reason to assume your users are lying to you. But it's always a good idea to include something in your app that'll allow for the users to submit an error from within the application.
http://groups.google.com/group/android-developers/browse_thread/thread/ddf6863e9a31052f?pli=1
you could use this project http://code.google.com/p/android-remote-stacktrace/ to verify