I have a android app in which Crittercism SDK is included and initialised as per standard documentation.
I intentionally put a loophole in the flow by which I can make app crash by manipulating data on my server and then pushing it to device.
Recently few users reported crash but I didnot see it on Crittercism website. So I simulated crashes. Out of 3 crashes I got report for 2 on Crittercism website and one was missed.
I waited for a day. And since 2 crashes made through, there is no issue with sdk integration in my app. (Its not NDK and crashes were of type malformed JSON during parsing) Not related to Java runtime crashes or other low level crashes.
Does any one face similar issue? How can we avoid this?
Thanks in advance.
I experienced a similar issue, but it concerned the automatic emails that you receive when a crash occurs. I found that identical crashes are usually only reported once.
The following Crittercism KB article explains why:
http://support.crittercism.com/articles/knowledge_base/Im-not-getting-an-email-every-time-the-app-crashes-whats-happening
Related
I want you to know I'm a newbie to Android Development.
I have developed an Android application (not uploaded on Google Play Store) with Crashlytics implemented.
This app is used by 50-60 users per day. Before releasing the app I tested it many times on my device and several others to check if it crashes or not. The app passed all the tests.
Now the app is crashing on some of the user's device and I can see the reason why it is crashing in Crashlytics dashboard.
But the app is crashing on specific devices only and working fine on other user's device and even after reproducing the issue on my device the app does not crash so I'm a bit confused about how to tackle problems like this.
And I can not purchase a device just for the purpose of testing.
So my questions are,
How can I solve the bugs in my app which are not reproducible on my devices?
Is it possible to know the exact reason why the app crashed using other bug reporting tools so that I can reproduce the bug on my device.
Any help is appreciated
Thank You :)
Try ACRA. You can implement sending crash reports to your email which will have model of the phone, android version, and stack trace of the crash.
There is a very high chance that many bugs and performance issue might get missed out during testing. Using production level SDKs like Finotes or Crashlytics to capture bugs with a detailed report which makes it easy to do the root cause analysis.
Crashlytics captures only crashes, Finotes captures many other types of bugs as well. Both SDKs are so lightweight and don't affect apps performance in production.
Somehow managed to fix bugs my app by using Mixpanel. Tracking an event was so much helpful.
Thanks Guys. :)
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.
I am developing android application for client. Now client testing my application in various device. While testing, my application is crash at times. Now I need to know when and where the application crash.
How can I get the crash report from the device? Since my client does not have sdk and eclipse to view logcat error report.
There are mechanisms like ACRA that will let you obtain the crash reports from Android apps.
Instabug is a bug & crash reporting service and it’s just what you’re looking for.
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.
By adding the Crash Report SDK in the project, You can view the released application crash log, which will help to locate problems.
Here is a demo page
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.
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