Re: [android-developers] Re: How to Track Down Force Closes?
I'm thinking of putting flurry in my app. Would it be possible to share your code on how you catch these and trigger flurry? Thanks, Wayne On Thu, Nov 26, 2009 at 5:24 AM, westmeadboy westmead...@yahoo.co.ukwrote: I use a combination of my own default uncaught exception handler and flurry's. When an uncaught exception occurs, I grab all the device, firmware and app version etc info and relevant lines from the stacktrace and put them in a Map (max 10 entries, but you can just fire off multiple events) which is then reported as an event using Flurry. Then I trigger Flurry's default uncaught exception handing. The problem with Flurry's default mechanism is it doesn't link the exception to the user paths so you are limited to the stacktrace to know the context of the exception (not always enough). Also, the amount of information it includes when reporting an uncaught exception, is fairly limited. Using this technique I have received valuable instant feedback of bugs in my code. Sometimes device specific, but usually gaps in my testing! A couple of times I've been able to release quick (emergency) bug fixes before 95%+ of my users had a chance to update the buggy version. I think I wouldn't have known about most (if not all) of these bugs had it not been for the analytics. I've not received a single bug report from users yet even though I know full well they've experienced several! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Writing code is one of few things that teaches me I don't know everything. Join the Closed Beta of Call Girl Manager http://www.fuligin.com/forums -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: How to Track Down Force Closes?
rflexor wrote: We have successfully implemented a crash-handler based on Thread.setDefaultUncaughtExceptionHandler(). You just have to make your ExceptionHandling-code fast and robust and must not rely on the availability of any resources. We just write the stacktrace to a file together with the versionnumber of our app. Whenever the application starts anew, it checks for any stacktrace-files on the SDCard, pops up a SorryForCrashingDialog and offers the user to send the stacktrace via mail to our bugreport- address. This approach has proved very helpful! Only problem are email- apps ignoring the regular email-intent-recipient-data :-D An example for creating crash-handlers can be found here: http://stackoverflow.com/questions/601503/how-do-i-obtain-crash-data-from-my-android-application DroidDrop was also recently released. And some analytics packages, like Flurry, also support collecting exception stack traces. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Warescription: Three Android Books, Plus Updates, $35/Year -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: How to Track Down Force Closes?
I use a combination of my own default uncaught exception handler and flurry's. When an uncaught exception occurs, I grab all the device, firmware and app version etc info and relevant lines from the stacktrace and put them in a Map (max 10 entries, but you can just fire off multiple events) which is then reported as an event using Flurry. Then I trigger Flurry's default uncaught exception handing. The problem with Flurry's default mechanism is it doesn't link the exception to the user paths so you are limited to the stacktrace to know the context of the exception (not always enough). Also, the amount of information it includes when reporting an uncaught exception, is fairly limited. Using this technique I have received valuable instant feedback of bugs in my code. Sometimes device specific, but usually gaps in my testing! A couple of times I've been able to release quick (emergency) bug fixes before 95%+ of my users had a chance to update the buggy version. I think I wouldn't have known about most (if not all) of these bugs had it not been for the analytics. I've not received a single bug report from users yet even though I know full well they've experienced several! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: How to Track Down Force Closes?
We have successfully implemented a crash-handler based on Thread.setDefaultUncaughtExceptionHandler(). You just have to make your ExceptionHandling-code fast and robust and must not rely on the availability of any resources. We just write the stacktrace to a file together with the versionnumber of our app. Whenever the application starts anew, it checks for any stacktrace-files on the SDCard, pops up a SorryForCrashingDialog and offers the user to send the stacktrace via mail to our bugreport- address. This approach has proved very helpful! Only problem are email- apps ignoring the regular email-intent-recipient-data :-D An example for creating crash-handlers can be found here: http://stackoverflow.com/questions/601503/how-do-i-obtain-crash-data-from-my-android-application Ralf -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
