There are two approaches to handling this, depending on what you want to accomplish.
There's a per-Activity flag in the manifest: android:finishOnTaskLaunch="true". Use this on individual activities which should disappear, because they are ephemeral by nature. If the overall nature of the application is that it only makes sense to start at the first task, then use android:clearTaskOnLaunch="true". You set this on your root activity. Launching will always bring up that activity; any others will be discarded. I've noticed that at least one app organizer I use doesn't respect this, however. But it works when (re)launching from the stock home application. ---------- Forwarded message ---------- From: JP <joachim.pfeif...@gmail.com> Date: Feb 15, 2:48 pm Subject: Force Close just restarts the app? To: Android Developers On Feb 13, 12:45 pm, Steeler <cowboyd...@yahoo.com> wrote: > I only have one activity in this app, but it still does it. What Dianne's saying is that multiple instances of the Activity reside on the activity stack, right on top of each other. I have a similar problem when the activity stack does not seem to clear on HOME. Next time the user exits through BACK, the previous instance of the activity is revealed as it sits on top now. To the user it looks as if the BACK button didn't work. -- 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
