Hi, I'm currently debugging with the Dev Tools, so this entire situation may be related to that. I'm not fully confident of that though, so I figured I'd check and make sure.
I have an Activity that is calling startActivityForResult on another activity. Because of the 'Immediately Destroy Activities ' setting, this activity is immediately destroyed after the child is launched. However, when the child activity finishes, the parent activity doesn't exist to return a result to, so the program just hangs on the black screen without doing anything. It's highly possible that this is related to the Dev Tools, so i'm not sure if it's possible for Android to kill a parent activity while its child its child is alive. But if that case is possible, i'm obviously not handling it. Any help or information to help me better understand the life cycle and situation would be wonderful! Thanks! -Tom (PS ~ I'm using this setting in order to help me force onSaveInstanceState correctly, so any advice you can give about would be helpful as well. thanks!)
-- 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
