3

The app has 2 tasks of activities:

  • TASK 1
    • Activity A (launcher)
    • Activity B
  • TASK 2
    • Activity C <---- that's where the stack points at in the example.

Now try that:

  1. Go to the recent apps carrousel (you know by clicking the button on the right of the Home button in newer phones).
  2. Swipe all the apps out.
  3. Your application is killed and a new Application instance is created (Application#onCreate() is called).
  4. Android tries to show the Activity C of the TASK 2.

The funny thing is that if you're here:

  • TASK 1
    • Activity A (launcher)
    • Activity B <---- here

...and you do repeat the scenario, your application is killed and android goes back to the Home screen as I think it should.

In short, it looks like Android does not clear all the tasks when killing the application. This is only true in that very precise scenario. Go to Settings > Applications > Your App > Force Stop, and you will see that it does clear all the tasks.

Anything we can do to force Android to kill all the tasks when killing the application?

Jordan
  • 551
  • 3
  • 11

2 Answers2

1

After looking at how the recent apps are handled on the Android SDK (see source here line 135 http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/4.0.1_r1/com/android/systemui/recent/RecentTasksLoader.java?av=f#135)

I understood (and tested) that if you provide Activity C with an icon and a label as such:

<activity
    android:name=".ActivityC"
    android:label="Activity Title"
    android:icon="@drawable/ic_icon"
</activity>

You will see 2 apps (tasks really) in the recent apps carrousel.

Now I'm thinking that for my use case I should not use different tasks because it's almost seen as another app from Android's standpoint.

Jordan
  • 551
  • 3
  • 11
  • I am having same scenario in my app. But I want behavior like when I reopen app from recents or from app launcher icon, I want task 2 with Activity C as my topmost activity. But Activity B of task 1 is getting visible in my app. Any solution? – gauri Apr 30 '15 at 12:51
  • When I lauch my app from notification, Activity B of task 1 is started. But after pressing back button Activity C of task 2 is getting visible which I don't want. – gauri Apr 30 '15 at 12:53
1

Tasks are meant to be created for independent jobs. That's why it's said that singleInstance and singleTask starts the Activity at the ROOT of new task (as the root activity for that particular task). Because when you click one of the tasks from Overview Screen, the Android system needs a way of launching the task (in that case, it needs a launcher/root activity).

So, one you kill one task, it shouldn't kill the other one since user might want to switch that INDEPENDENT app task later right?

But it's hard to manage that behaviour since you need to properly handle (mostly navigation and user experience) saperate tasks. So think before you act that way. Android document itself says so;

"The other modes — singleTask and singleInstance — are not appropriate for most applications, "

stdout
  • 2,471
  • 2
  • 31
  • 40