StartActivity does not start the correct activity

You can call StartActivity from a service.

I've tried to reproduce it and it seems to work correctly.
Will it be possible to upload a small project that demonstrates this issue?

Hmm, I will try to create a small project which shows the problem.

Ok, created a small project and found out some more info.

The problem seems to be the activity that is the first on the activity stack. This one is never brought to front again.

To reproduce it:

- Install the app.
- exit app with back key (so no activity is on the stack)
- add the widget AATestWidget to the homescreen
- Press button Act2 to start the Activity 2 (green)
- Press Home to return to Homescreen
- Press button Act3 to show Activity 3 (red)
- Press home
- Press button Act2

Activity 3 is then shown.

If you always use the home button to return to the homescreen you can switch between Main and Activity3 from the widget, but Activity2 does not show.

If you start with another activity so this one is the first on the stack then you can't return to this one with the widget.

Perhaps this is a Android problem? I currently Use Gingerbread 2.3.3

This seems to be the standard behavior when starting an activity from a service. I tried to use different flags in the internal Intent and the result is the same.

Thanks for checking it.

It's really strange. I would call it a bug (in Android). I think I will search if someone else had this same issue.

Did you try different launchModes (others than singleTop)?

This is not really a bug. This is the default "launcher" behavior.

I didn't try different launch modes, only different flags in the intent. I haven't tried FLAG_ACTIVITY_MULTIPLE_TASK which might work, as it will probably have other unwanted side effects.

You can workaround this issue in your application. Check the value of Activity.GetStartingIntent in Activity_Resume and start the correct activity (I haven't tested it...).

Not sure if this is the same but I had a similar issue with an app that has 2 launcher shortcuts and sometimes one shortcut opened the other activity. I overcame it by modifying android:launchMode in Manifest file to "singleInstance", for the activity that was not getting launched correctly.