Yes I'm good with all that. My question is: Why doesn't the app starts from the initial entry point screen? Why does it try to start from the last opened Activity since the process has effectively being killed.
Ex. app launched and ActivityA(entry point of the app) starts, from there I go to Activity2, then Activity3 and press Home. In the mid time the process gets killed by the OS, I then launch the app and instead to start from Activity1 it does from Actitvity3.... Thanks! On Sep 23, 4:10 pm, Mark Wyszomierski <[email protected]> wrote: > Yeah I think by default if the app is not resumed for some period of > time, android will restart the app instead of resuming it: > > http://developer.android.com/guide/topics/manifest/activity-element.html > > look at: "android:alwaysRetainTaskState" > > On Sep 23, 11:01 am, Albert <[email protected]> wrote: > > > > > Hi, > > > I'm having a very odd issue. I launch my app, use it then press the > > "Home" key and the app pauses and goes to the background. I can also > > resume it by launch it again, so far so good but if I leave it sitting > > on the background for a couple of hours and try to launch it, it calls > > onCreate() (on the paused activity) instead of just resuming, > > therefore loosing the previous state, it behaves as that screen is the > > entry point of the app. > > > Has anyone seen a similar issue. Does someone know if this is a normal > > behaviour?? What I am missing here? > > > Thanks, > > Alberto -- 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
