Just curious since you and others have asked similar questions in the past. I just wrote a simple App with ActivityA and ActivityB where A is singleTask launchMode. If I go A->b->Home->relaunch I get gack to B. So I cannot replicate the scenario you describe. The code and all files for the app are just a couple of dozen lines so I can post if here if that would be helpful to figure out what you are doing differently than my test.
On Feb 18, 7:09 am, Mark Wyszomierski <mar...@gmail.com> wrote: > Hi, > > I have an activity, ActivityA, and its launchMode is set to > "singleTask". > > I start the application from the app tray. ActivityA launches > ActivityB from a button click. ActivityB is a normal activity with no > launchMode set ("standard"). > > With ActivityB on top of the activity stack, I hit the home button, > then resume the app, I see ActivityA instead of ActivityB when > resumed. > > Shouldn't the history stack be preserved in this case, and B be > showing? When I resume, I see A get onNewIntent() called, and I'm not > sure why this is happening. I thought the stack would be preserved. > > Thanks -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en