On Jan 18, 12:50 am, Zsolt Vasvari <[email protected]> wrote: > > But don't ever let an exception fall through in the main thread that > > runs your activities because your app will terminate with an > > unfriendly "force close" dialog that users are conditioned to hate. > > I don't agree with this advice. How are you going to fix problems if > you stick your head in the sand. At least when you Force Close, you > don't let the app continue in a potentially invalid state messing > eveyrthing up.
I'm not advocating a complete ignorance of exceptions that indicate trouble. I'm just saying that if you allow something to fall through the cracks, a force close will happen and users hate that. A comprehensive solution would be to set an uncaught exception handler on the main thread of the app so that you can trap when these things happen and set up your own graceful response, including a more friendly error message, an attempt at recovery (don't be so pessimistic about the state of the system) and a report to Flurry with some context to help you diagnose the problem. The market reporting tools don't always tell you everything you want to know and the user may not choose to report the problem anyway. Doug -- 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

