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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
