On Wed, Jun 23, 2010 at 7:57 AM, Alexey Kryshen <[email protected]> wrote:
> If child activity started by the startActivityForResult() exit by > unexpected exception the > onActivityResult() is not called and I have no any ideas how can I handle > this to get application working in a fail-safe manner ? > You can register an uncaught exception handler to catch any exceptions that are not otherwise handled properly. > When my code runs child activity with startActivityForResult() it awaits > until onActivityResult() will be invoked to get working further, but > onActivityResult() is not calling and my code is "hang- up" (logically). > This is strange. AFAIK, if any activity in your stack crashes, your who Application comes down with it. You should not be "stuck", especially since startActivityForResult() doesn't block - it just starts the child activity then waits for a return value in onActivityResult(). Unless you're doing something that prevents the app from functioning until a valid response is obtained. ------------------------------------------------------------------------------------------------- TreKing - Chicago transit tracking app for Android-powered devices http://sites.google.com/site/rezmobileapps/treking -- 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
