Most of the Crash will be tried to solve but then and there. ARCA helps me to show a Toast or a Dialog but that Kills my Application after that. (But it can be used for Reporting)
I dont want my Application to be killed. Is it Possible that My all Activity being started my another Looper not the Native Main Looper then What I can do is have a try catch at Looper.loop(). So that Main Looper is not affected. But user has to *Thanks & Regards,* *Vivek Khandelwal* *Mob: 8056062979* On Fri, Mar 23, 2012 at 3:29 PM, Kostya Vasilyev <[email protected]> wrote: > The main looper is special, just because you have _a_ looper in _a_ thread > doesn't mean it will now handle all UI interaction. > > I'd suggest (the list is clearly out of sequence): > > 1. Fix the crashes so they don't happen anymore (at least not so much). > > 2. In your crash handler, forget about touching the UI, rather create a > log file, and include a summary of recent application activity (e.g. a > dozen or so most recent queries, the user's activity, whatever else you > think should be useful). > > 3. Consider using ACRA as your error reporting solution. > > -- > 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 > -- 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
