By Martin

2011-04-26 18:03:11 8 Comments

In Android I have some activities, let's say A, B, C.

In A, I use this code to open B:

Intent intent = new Intent(this, B.class);

In B, I use this code to open C:

Intent intent = new Intent(this, C.class);

When the user taps a button in C, I want to go back to A and clear the back stack (close both B and C). So when the user use the back button B and C will not show up, I've been trying the following:

Intent intent = new Intent(this, A.class);

But B and C are still showing up if I use the back button when I'm back in activity A. How can I avoid this?


@Arnaud 2020-01-18 16:50:38

you wont get any activity pressing back button after that :


@Gibolt 2020-01-08 02:33:49

Advanced, Reuseable Kotlin:

You can set the flag directly using setter method. In Kotlin or is the replacement for the Java bitwise or |.


If use this more than once, create an Intent extension function

fun Intent.clearStack() {

You can then directly call this function before starting the intent


If you need the option to add additional flags in other situations, add an optional param to the extension function.

fun Intent.clearStack(additionalFlags: Int = 0) {
    flags = additionalFlags or Intent.FLAG_ACTIVITY_NEW_TASK or Intent.FLAG_ACTIVITY_CLEAR_TASK

@Jake Basile 2011-04-26 18:10:07

Try adding FLAG_ACTIVITY_NEW_TASK as described in the docs for FLAG_ACTIVITY_CLEAR_TOP:

This launch mode can also be used to good effect in conjunction with FLAG_ACTIVITY_NEW_TASK: if used to start the root activity of a task, it will bring any currently running instance of that task to the foreground, and then clear it to its root state. This is especially useful, for example, when launching an activity from the notification manager.

So your code to launch A would be:

Intent intent = new Intent(this, A.class);
CurrentActivity.this.finish(); // if the activity running has it's own context

// view.getContext().finish() for fragments etc.

@Martin 2011-04-26 18:30:44

Thanks but I've tried this. Still when I tap the back button after it shows C again. What can I be missing?

@Jake Basile 2011-04-26 18:35:36

How do you declare your activities in AndroidManifest.xml?

@Martin 2011-04-26 18:46:13

I've tried with android:launchMode="singleTop" but that didn't make any difference. I can't see what is wrong. So when you use this code and hit back button C will not show up?

@Jake Basile 2011-04-26 18:53:25

Are all the activities declared with the same taskAffinity?

@Jake Basile 2011-04-26 18:55:48

Huh, this doesn't work for me either. It should... I'll look into it.

@Jake Basile 2011-04-26 18:59:16

Try it with intent.addFlags(int), that made it work for me. I bet setFlags overrides the previous flags, so only NEW_TASK was getting added.

@Martin 2011-04-26 19:24:56

So irritating, I restarted the emulator and eclipse, cleaned the project and now it seems to be working just like you said. I mark this as the answer as this was the first one.

@Jake Basile 2011-04-26 19:42:47

Glad I could "help". Restarting Eclipse and the emulator tend to be near the top of my troubleshooting list.

@Kyle Clegg 2012-06-08 09:41:40

I have been frustrated with this for a couple hours now, with NOTHING seeming to work. I just realized that I am using Action Bar Sherlock SherlockActivities and not normal Android activities. Could this have something to do with it?

@dzeikei 2012-06-19 04:18:24


@Mike Repass 2012-09-17 23:17:30

@Kyle I struggled with this as well, take a look at:

@2cupsOfTech 2014-07-23 17:08:37

doesn't work for me however calling finish() on source activity does what I needed to achieve

@Arno 2014-10-06 12:32:24

I had the same problem that this was not working. What fixed it for me was to call finish() after starting the new activity

@Hong 2014-11-18 02:41:16

@Arno Thank you! finish() did it. I would never have thought of it without your tip.

@Kevin D. 2015-01-29 02:49:28

Use addFlags not setFlags, figured it out the hard way. Also added Intent.FLAG_ACTIVITY_NEW_TASK

@Sam 2016-04-27 12:49:32

I also added one more clear Intent intent = new Intent(SingUpActivity.this, LoginActivity.class); intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_CLEAR_TASK | Intent.FLAG_ACTIVITY_CLEAR_TOP); startActivity(intent); finish();

@Pedro Okawa 2018-01-17 18:49:39

That's a good answer, but it may be replaced by without calling finish on current activity: Intent intent = new Intent(this, A.class); intent.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TASK | Intent.FLAG_ACTIVITY_NEW_TASK); startActivity(intent);

@steven smith 2018-10-14 04:42:27

Also, for APK21+ there is finishAndRemoveTask.

@Pankaj Talaviya 2017-03-10 10:10:24

Use this code for starting a new Activity and close or destroy all other activity stack or back stack.

Intent intent = new Intent(this, MainActivity.class);

@Mohamed Mo'nes 2019-09-03 12:35:57

for me adding Intent.FLAG_ACTIVITY_CLEAR_TASK solved the problem

Intent i = new Intent(SettingsActivity.this, StartPage.class);

@Shohan Ahmed Sijan 2019-07-08 11:02:19

This code work for me in kotlin:

 val intent = Intent(this,

@5chw4hn 2019-03-15 12:44:55

This is how I solved the problem:

private boolean clearHistoryBackStack = true;

public final void finish() {


@stevyhacker 2019-02-28 00:18:50

Kotlin example:

      val intent = Intent([email protected],
      intent.flags = Intent.FLAG_ACTIVITY_CLEAR_TOP or Intent.FLAG_ACTIVITY_NEW_TASK

@Mujeeb Rahaman T 2019-02-19 11:33:41


@Exigente05 2019-01-23 20:59:52

In kotlin it is almost same like java. Only | symbol is replaced by or text. So, it is written like-


@Sujith Royal 2018-09-12 10:01:37

I found an interesting solution which might help. I did this in my onBackPressed() method.


FinishAffinity removes the connection of the existing activity to its stack. And then finish helps you exit that activity. Which will eventually exit the application.

@PhilipS 2018-03-12 11:56:58

This worked for me with onBackPressed:

public void onBackPressed()
    Intent intent = new Intent(ImageUploadActivity.this, InputDataActivity.class);

    Intent myIntent = new Intent(this, ImageUploadActivity.class);

@Firzan Shaikh 2017-10-28 06:53:39

Use finishAffinity() to clear all backstack with existing one.

Suppose, Activities A, B and C are in stack, and finishAffinity(); is called in Activity C, 

    - Activity B will be finished / removing from stack.
    - Activity A will be finished / removing from stack.
    - Activity C will finished / removing from stack.

@Guilherme Junqueira Coutinho 2017-09-18 19:37:15

This is a really old answer and i didn't really found a proper solution to it, to the sole purpose of clearing the backStack, i decided to create my own backstack, which is not even a stack tbh, but it doesn't have to be, since we want to clear everything in it anyways;

Theres an overhead of handlind the backstack everytime, but it gave me the control i needed;

First Declare a public static List of Activities (or fragments, whatever you need);

public static ArrayList <Activity> backStack = new ArrayList<>();

And inside all other activity's onCreate method:


And finally, when you want to clear the backstack, simply call:

public static void killBackStack () {
    for (Activity ac : backStack) {
        if (ac != null)

@Pankaj Talaviya 2017-09-07 05:03:31

Use setFlags() method for clear back side opened all activity close and start yourActvity

Intent intent = new Intent(getApplicationContext(), yourActivity.class);

@baswaraj 2016-12-15 14:49:43

Use finishAffinity(); in task C when starting task A to clear backstack activities.

@nuttynibbles 2017-02-03 15:30:13

only this answer works for me. Intent.FLAG_ACTIVITY_CLEAR_TOP and Intent.FLAG_ACTIVITY_NEW_TASK are not required

@Maximus 2011-04-26 18:06:29

It sounds to me like you need to start Activity C from Activity B by using startActivityForResult(). When you click a button in Activity C, call setResult(RESULT_OK) and finish() so Activity C is ended. In Activity B, you could have the onActivityResult() respond by also calling finish() on itself, and you'd then be taken back to Activity A.

@Guillaume Brunerie 2011-04-26 18:10:26

Yes, but if there are 42 activities between A and C, this will be rather tedious. The flag FLAG_ACTIVITY_CLEAR_TOP is supposed to do directly what the OP want.

@Jake Basile 2011-04-26 18:15:18

This would be a less than optimal way of achieving what the OP wants, and as @Guillaume said, it would require code in all of the activities between the root and the top of the stack.

@Maximus 2011-04-26 18:16:22

Duly noted. These are flags I need to learn about apparently.

@Ashish Saini 2016-04-01 07:47:13

Intent.FLAG_ACTIVITY_CLEAR_TOP will not work in this case. Please use (Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_CLEAR_TASK)

For more detail please check out this documentation.

@Renjith JR 2016-04-01 09:27:34

Either add this to your Activity B and Activity C


or Override onBackPressed function to avoid back pressing with a return.

public void onBackPressed() {

@Muhammad Aamir Ali 2013-05-16 07:58:03

Try using


and not


@Tarun 2016-04-19 05:41:16

I tried all solutions and none worked individually for me. My Solution is :

Declare Activity A as SingleTop by using [android:launchMode="singleTop"] in Android manifest.

Now add the following flags while launching A from anywhere. It will clear the stack.

Intent in = new Intent(mContext, A.class);

@Vipin Yadav 2016-07-12 11:55:21

You can use this example to call your Activity A from Activity C

Intent loout = new Intent(context, LoginActivity.class); loout.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_CLEAR_TASK); context.startActivity(loout);

@blackjack 2016-09-27 10:41:58

In manifest




@Jaydeep purohit 2016-04-13 12:42:52

If your application has minimum sdk version 16 then you can use finishAffinity()

Finish this activity as well as all activities immediately below it in the current task that have the same affinity.

This is work for me In Top Payment screen remove all back-stack activits,

public void onBackPressed() {
        startActivity(new Intent(PaymentDoneActivity.this,Home.class));

@Dominik Helleberg 2011-06-28 20:38:24

What about adding in manifests file for related activity :


to the activity definition of B and C ? They will not be added to the backstack. Not sure if that is what you want.

@Skynet 2015-03-02 12:26:15

Be very careful while using this - If you are using login with FB or any similar sort of functionality

@Alfie Woodland 2015-03-12 16:32:32

@Skynet Why? What are the problems associated with doing this?

@Skynet 2015-03-13 07:18:01

When you pass control to FB for login from a page with nohistory as true, the FB app does not now where to land after loging the user in, in my case it was returning to the phone home screen and I almost lost my job!

@Tarun 2016-04-19 05:17:40

This does not let an activity addded to backstack....this is not correct solution.

@Masum 2018-06-26 10:50:21

Exactly i am looking for

@Yannick 2018-11-15 20:29:01

Only thing which worked out for me

@diesel 2012-12-03 20:10:35


@Aviel Gross 2015-03-08 06:31:16

With all respect to the CLEAR_TOP flag - this combination is the ONLY one that completely cleared the entire stack and made the new activity the only one in the app. Thank you!

@Yuri Heupa 2015-09-24 01:59:06

What's the diff between this and the accepted answer?

@March3April4 2016-11-06 08:07:27

This was perhaps what I was looking for. Works great!

@Pablo Cegarra 2017-02-16 12:51:40

Thanks, the difference with the accepted answer is that with this flag we dont need to call activity.finish

@Woppi 2017-12-27 11:22:05

With this setup, when I click back, it closes the app.

@Shamsul Arefin Sajib 2018-05-09 13:10:49

FLAG_ACTIVITY_CLEAR_TASK worked perfectly together with NEW_TASK

@MD Danish Ansari 2018-07-25 15:10:56

This should be the accepted answer. Thank you very much.

@Jonny 2020-04-20 21:43:31

This one worked for me, the accepted one did not. Thanks.

@Daniel Schuler 2013-05-29 22:58:48

Starting in API 16 (Jelly Bean), you can just call finishAffinity().

Now you can also call ActivityCompat.finishAffinity(Activity activity) with the compatibility library.

Be sure to set taskAffinity in the manifest to a package name unique to that group of activities.

See for more info:

@PhilippS 2014-12-08 20:47:38

Realy userful and easy solution if you are alread on API 16. Worked for me!

@Ryan 2015-08-28 23:09:33

reminder: this will only work for activities in that share the same taskAffinity name

@arsent 2016-10-05 19:51:42

this only work if you have just one activity in the history.

@Arun Sharma 2015-06-10 06:15:25

Add NO History Flag in the intent.

In activity B, start the activity C as below >>>>>>

Intent intent = new Intent(this, C.class);
intent.setFlags(intent.getFlags() | Intent.FLAG_ACTIVITY_NO_HISTORY); 

@GeetT 2015-05-17 03:09:02

For future research, try this code.

Intent intent = new Intent(context, LoginActivity.class);

@Janne Oksanen 2015-08-20 13:23:23

These flags finally worked for me. What I did was I started the same Activity I was in with these flags and a boolean extra EXIT=true. The in onCreate() I checked the launch parameters for EXIT and called finish() if it was set true. That's a lot of hassle just to close your own app.

@Swap-IOS-Android 2014-10-31 12:08:53

i called activity_name.this.finish() after starting new intent and it worked for me.


But it won't work for me... I am not suggesting this solution for use but if setting flag won't work for you than you can try this..But still i recommend don't use it

Related Questions

Sponsored Content

50 Answered Questions

[SOLVED] Is there a unique Android device ID?

10 Answered Questions

53 Answered Questions

15 Answered Questions

[SOLVED] Removing an activity from the history stack

104 Answered Questions

[SOLVED] Close/hide android soft keyboard

27 Answered Questions

[SOLVED] What and where are the stack and heap?

11 Answered Questions

[SOLVED] Proper use cases for Android UserManager.isUserAGoat()?

10 Answered Questions

[SOLVED] Android: Clear Activity Stack

14 Answered Questions

[SOLVED] Clear back stack using fragments

Sponsored Content