Home/ Questions/Q 4099576
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T20:27:07+00:00

I know there’s been a few posts for what I’m about to ask but

  • 0

I know there’s been a few posts for what I’m about to ask but I can’t find any with the right answer.

From my understanding, if your main activity’s (let’s call it A) launchMode is set to singleTask, and A has initiated activity B then a click to the home button will destroy the history stack and re-launching the application will take you back to A and not B.

I have launchMode set to singleTask because I have a persistent notification and I don’t want to have multiple instances of the main activity to appear whenever the user clicks on the notification.

Is there something I’m missing that would allow me to cater for both?

So I’m asking if there’s a way I can ensure that whenever the user wishes to launch the app, from the notification or not, to take him back to the last (current) activity.

If I change launchMode to singleTop it works but I get multiple instances of the main activity whenever I launch it.

Thanks

Andreas

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Have you tried setting launchMode to singleTop to all the activities in your app?? Because what i get from your query is that the main activity isn’t singleTop, so that might lead to another instance of the main activity being called once the main activity is launched from the activity that was launched from the notification activity.

    Or you can specify the launchMode as an attribute to the application tag itself in the manifest.

    • 0