IssueTracker

I have a small test program with 2 activities:
SingleInstanceActivity has launchMode="singleInstance" and
SingleTopActivity has launchMode="singleTop".

The SingleInstanceActivity calls startActivity() to start SingleTopActivity without any additional Intent flags like this:

  Intent intent = new Intent(this, SingleTopActivity.class);
  startActivity(intent);


- Steps to reproduce the problem:

Using the attached code, do the following:
1. Launch the program "SingleTop bug" from the home screen
2. Click FIRST button "Start Activity without FLAG_ACTIVITY_SINGLE_TOP"
3. See SingleTop Activity shows onCreate(), onStart(), onResume()
4. Click the HOME button to return to the home screen
5. Launch the program "SingleTop bug" from the home screen again
6. Click FIRST button "Start Activity without FLAG_ACTIVITY_SINGLE_TOP"
7. See SingleTop Activity shows onPause(), onStop(), onStart(), onResume() however onNewIntent() is never called.

- What happened:

The first time SingleTopActivity is launched without FLAG_ACTIVITY_SINGLE_TOP, onCreate() and onResume() are called in SingleTopActivity. This is correct.
The second time SingleTopActivity is launched without FLAG_ACTIVITY_SINGLE_TOP, onResume() is called in SingleTopActivity, BUT onNewIntent() is NOT called in SingleTopActivity. This is incorrect.

- What you think the correct behavior should be:

The correct behavior should be as documented in the description of "launchMode" at http://developer.android.com/guide/topics/manifest/activity-element.html#lmode

"...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 an onNewIntent() call); a new instance is not created."

I have tried this on several different devices and several versions of Android OS (2.2, 2.1, 1.6) so it looks like it has been there for awhile.

Please see also issue 36909641 (reported October 2009 on SDK 1.6 and still open) describing same problem.

NOTE: The attached code also has a second button labelled "Start Activity with FLAG_ACTIVITY_SINGLE_TOP". Using this demonstrates the correct behaviour. It is therefore REQUIRED to set FLAG_ACTIVITY_SINGLE_TOP when launching a SingleTop activity to achieve the behavior described in the documentation.