On Fri, Mar 23, 2012 at 5:43 AM, Vivek Khandelwal < [email protected]> wrote:
> 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. > Then test your application thoroughly and reduce the number unhandled exceptions. If your application hit an unexpected error and gets to the unhandled exception handler, you're pretty much past the point of no return. Given how many things could have caused you to crash and how many places you could have crashed from, this is just not realistic. What if you hit an exception in B as you launch it from A? Then you close B and go back to A. Then you relaunch B and hit the error again and go back to A. Is that better? If your concern is getting the details of the crash to fix it later, then I echo the recommendation to use ACRA. But trying to recover and continue from an unhandled exception, which has the clear potential to put you into an infinite loop of crashing and recovering if you do even manage it, is a futile attempt. Don't fight it - instead, fix your bugs so it doesn't happen (or at least happens rarely). ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- 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
