That's what I thought, but it is definitely not doing that. logcat is showing the relevant lifecycle actions being called, but for some reason the result from C is not making it back to B. Nothing for onActivityResult() displays at all.
The only thing I can think of is that I am missing something in my Manifest file or that I'm not calling the Intent with the correct context in the constructor ( I'm using new Intent(B.this, code) from inside the button at the moment). Any suggestions on where to go/what to do to figure this out? On Oct 22, 10:55 pm, hackbod <[EMAIL PROTECTED]> wrote: > You'll receive the result immediately prior to onResume(). > > On Oct 22, 7:41 pm, Alvin Yates <[EMAIL PROTECTED]> wrote: > > > Under what conditions is onActivityResult() supposed to be called? > > I'm trying to debug this issue I am having with my app which is a > > normal "press button to save and return" thing and it seems like that > > never happens. For example: > > > Activity sequence: A -> B -> C. Each app goes to the new one by > > startActivityForResult(thisActivity, nextActivity.class) on a button > > press. > > > I'm trying to make C such that saving data on C sends me to A, then to > > another activity. What instead happens is when I "setResult()/ > > finish()", the onActivityResult for B is completely ignored. I feel > > like it's something simple I'm missing, but don't see what it is at > > all. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
