I have exactly the same problem as you. And I made the same hack. It works fine for the cases when the started activity crashes. However, there is another case when onActivityResult() is broken:
-limit the number of process to 1 in dev setting -start your activity -let your activity call startActivityForResult() -go to the home screen -return to your task -press back -onActivityResult() is not called The sub-activity has closed normally, so RESULT_CANCELED is not what you want but you will get it if using the hack. Android is so disappointing... -- 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
