The only solution I was able to find was to check a global static variable in every instance of onCreate() and finish if that variable had been reset to null, indicating the task had been restarted. I close all activities down to my root activity and start over. Soon I hope to have my app … Read more
I figured out what is wrong… The config is right, but I started application for debugging from Eclipse, this was the issue. Case # 1. Debug > A > B > HOME > A Get: A (stack is cleared) Case # 2. Debug > A > BACK > A > B > HOME > A … Read more
My suggestion would be to finish the activity that you don’t want the users to go back to. For instance, in your sign in activity, right after you call startActivity, call finish(). When the users hit the back button, they will not be able to go to the sign in activity because it has been … Read more
This is not a bug. When an existing singleTask activity is launched, all other activities above it in the stack will be destroyed. When you press HOME and launch the activity again, ActivityManger calls an intent {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER]flag=FLAG_ACTIVITY_NEW_TASK|FLAG_ACTIVITY_RESET_IF_NEEDED cmp=A} So the result is A > B > HOME > A. It’s different when A’s launchMode … Read more
Add this to onCreate and you should be good to go: // Possible work around for market launches. See https://issuetracker.google.com/issues/36907463 // for more details. Essentially, the market launches the main activity on top of other activities. // we never want this to happen. Instead, we check if we are the root and if not, we … Read more