Hi all, I am using Android 2.0 and have the following situation:
Activity A - has the attributes android:finishOnTaskLaunch="true" and android:allowTaskReparenting="true" This activity belongs to a task that has a service running and is usually not killed, so even when I am in the home screen I see the task running on DDMS (I will call it Task A). It is possible to start Activity A from another application (running on Task B). When it is launched, I assume Activity A is "reparented" to the Task A. I assume that, because the debugger stops on the breakpoint I have set on onCreate and I am debugging Task A only. Please, advise if this is not correct. So at this point, as far as I can tell, Task A has only Activity A. When in this situation, the service running on Task A receives some event and puts a notification on the Notification bar. This notification, if clicked, will send an Intent that also starts Activity A (this Intent has flags FLAG_ACTIVITY_NEW_TASK and FLAG_ACTIVITY_CLEAR_TOP). Now to the problem, what I expected is that, because of the CLEAR_TOP flag, Activity A would be destroyed and recreated, as it has standard launch mode. But what I observe is that another Activity A launches on top of the previous one. When I click BACK on the new instance of Activity A, the old instance is redisplayed, what for my use case is wrong. Note that this only happens when launching Activity A from another application. If I launch it from my application and click on the event on the notification bar, it is destroyed and relaunched. Anyone knows what could be the problem? 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
