My app has notifications, which - obviously - without any flags, start a new activity every time so I get multiple same activities running on top of each other, which is jus
Since you say you want to start your activity if it's not started already, maybe you wouldn't mind restarting it. I tested a ton of suggestions and flag combinations for the intent as well, this will always bring the activity you need to the front, though it won't keep any state previously associated with it.
intent.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TASK|Intent.FLAG_ACTIVITY_NEW_TASK);
API11+ only.
I had a similar issue after adding notifications as found on the android training site. None of the other answers here worked for me, however this answer did work for me. Summary:
final Intent notificationIntent = new Intent(context, YourActivity.class);
notificationIntent.setAction(Intent.ACTION_MAIN);
notificationIntent.addCategory(Intent.CATEGORY_LAUNCHER);
notificationIntent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
I think the best way to do it and in a simple manner is to start the activity normally, but set that activity in the manifest with the singleInstance
property. With this you practically approach both issues you are having right now, by bringing the activity to the front all the time, and letting the OS automatically create a new one if no activity exists or bring to the front the currently existing activity (thanks to the singleInstance
property).
This is the way an activity is declared as a single instance:
<activity
android:name=".YourActivity"
android:launchMode="singleInstance"/>
Also to avoid a choppy animation when launching through singleInstance, you could use instead "singleTask", both are very similar but the difference is explained here as per Google's documentation:
<activity
android:name=".YourActivity"
android:launchMode="singleTask"/>
singleInstance is the same as "singleTask", except that the system doesn't launch any other activities into the task holding the instance. The activity is always the single and only member of its task.
Hope this helps.
Regards!
I think what you need is in singleTop
Activity
, rather than a singleTask
or singleInstance
.
<activity android:name=".MyActivity"
android:launchMode="singleTop"
...the rest... >
What the documentation says does perfectly suit your needs:
[...] a new instance of a "
singleTop
" activity may also be created to handle a new intent. However, if the target task already has an existing instance of the activity at the top of its stack, that instance will receive the new intent (in anonNewIntent()
call); a new instance is not created. In other circumstances — for example, if an existing instance of the "singleTop
" activity is in the target task, but not at the top of the stack, or if it's at the top of a stack, but not in the target task — a new instance would be created and pushed on the stack.
On top of that (no pun intended), I had exactly the same need as you. I tested all the launchMode
flags to figure out how they actually behave in practice and as a result singleTop
is actually the best for this: no weird animation, app displayed once in the recent applications list (unlike singleInstance
that displays it twice due to the fact it doesn't allow any other Activity
to be part of its task), and proper behavious regardless the target Activity
already exists or not.
I know it is old, but nothing from the above were fitting to my application.
Without changing manifests and other configuration, here is the code to bring your app back to front - or opening it when it is closed
Intent notificationIntent = context.getPackageManager().getLaunchIntentForPackage(context.getPackageName());
notificationIntent.setPackage(null); // The golden row !!!
notificationIntent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_RESET_TASK_IF_NEEDED);
You can use this:
<activity
android:name=".YourActivity"
android:launchMode="singleTask"/>
which will work similar to "singleInstance"
but it won't have that weird animation.