Personally, I would use Thread.setDefaultUncaughtExceptionHandler() to eliminate the force-close dialog and deal with the unexpected exception myself, such as logging it to a server. This does not require a remote process.
On Wed, Nov 10, 2010 at 4:29 AM, Dianne Hackborn <[email protected]> wrote: > On Wed, Nov 10, 2010 at 1:25 AM, William Ferguson > <[email protected]> wrote: >> >> Um, I think the point that Lance was trying to make was that he won't >> actually know about the force close UNLESS he uses the remote service. >> But sure, once he knows about, then he could fix it. > > If the user hits the report button, the crash information will be available > through market feedback. > If you are just catching the error to report it yourself, there wouldn't be > a crash dialog, so no button for the user to press to kill the app before > you are done. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 3.0.1 Available! -- 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
