onActivityResult do not fire if launch mode of activity is singleInstance

Question

I have an Activity which is basically my main activity and its launch mode is single instance. But because of singleInstance, the onActivityResult() callback does not fire. And if I change the launch mode in my manifest file to any other mode it works fine.

Can you explain why this callback is not working?

score 50 · Accepted Answer · edited Sep 14 '17 at 13:11

50

I believe that the problem is that singleInstance doesn't let the callee activity to exist in the same task as the caller, hence it can't return the value to the caller.

Consider using singleTask instead:

singleTask

The system creates the activity at the root of a new task and routes the intent to it. However, if an instance of the activity already exists, the system routes the intent to existing instance through a call to its onNewIntent() method, rather than creating a new one.

singleInstance

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.

http://developer.android.com/guide/topics/manifest/activity-element.html

edited Sep 14 '17 at 13:11

David Wasser

93,459
16
209
274

answered Feb 25 '11 at 15:15

Pedro Loureiro

11,436
2
31
37

8

If `onActivityResult` depends on having both parent and child in the same task, shouldn't that be documented somewhere??? I'm dealing with an intermittent failure to call through `onActivityResult` wtf. – mwengler Jul 29 '12 at 19:33
3

I don't believe this is correct, I tried it and SingleTask did not fire onActivityResult when it finished. This StackOverflow seems to indicate the same thing: http://stackoverflow.com/questions/8960072/onactivityresult-with-launchmode-singletask – jt-gilkeson Jun 21 '13 at 00:26
@jt-gilkeson the question you linked to is talking about the launch mode of the **target** `Activity` (ie: the one you are trying to launch. OP's question is talking about the launch mode of the **calling** `Activity` (ie: the one calling `startActivityForResult()`). This answer is correct because an `Activity` with launch mode `singleTask` **can** launch other activities into its task (but an `Activity` with launch mode `singleInstance` cannot). – David Wasser Sep 14 '17 at 13:16

score 5 · Answer 2 · edited Jan 29 '12 at 10:14

5

If an activity is singleInstance, it will be the only one in the task so it always be the top of the task. So when you call startActivityForResult it will fire the callback method immediately.

edited Jan 29 '12 at 10:14

Aliaksei Kliuchnikau

13,589
4
59
72

answered Jan 29 '12 at 09:06

George

51
1
1

score 4 · Answer 3 · answered Feb 25 '11 at 15:06

A "singleInstance" activity, permits no other activities to be part of its task. It's the only activity in the task. If it starts another activity, that activity is assigned to a different task. The activity is always the single and only member of its task.
I think onActivityResult will not work with singleInstance

score 3 · Answer 4 · answered Feb 23 '18 at 16:06

3

You can't use singleInstance or singleTask with startActivityForResult method.

Standard mode or singleTop launch mode will fix the problem.

answered Feb 23 '18 at 16:06

Kirill Vashilo

1,559
1
18
27

score 0 · Answer 5 · answered Apr 24 '18 at 05:25

Android Source Code

Check "ActivityStarter.computeLaunchingTaskFlags()" method:

            } else if (mSourceRecord.launchMode == LAUNCH_SINGLE_INSTANCE) {
            // The original activity who is starting us is running as a single
            // instance...  this new activity it is starting must go on its
            // own task.
            mLaunchFlags |= FLAG_ACTIVITY_NEW_TASK;

That's the reason why NEW_TASK flag is added when your original activity with single instance launch mode.

More Source Code

Check "ActivityStarter.sendNewTaskResultRequestIfNeeded()" method:

        if (sourceStack != null && (mLaunchFlags & FLAG_ACTIVITY_NEW_TASK) != 0) {
        // For whatever reason this activity is being launched into a new task...
        // yet the caller has requested a result back.  Well, that is pretty messed up,
        // so instead immediately send back a cancel and let the new task continue launched
        // as normal without a dependency on its originator.
        Slog.w(TAG, "Activity is launching as a new task, so cancelling activity result.");
        sourceStack.sendActivityResultLocked(-1 /* callingUid */, mStartActivity.resultTo,
                mStartActivity.resultWho, mStartActivity.requestCode, RESULT_CANCELED,
                null /* data */);

That's the reason why FLAG_ACTIVITY_NEW_TASK always immediately return RESULT_CANCELED.

score 0 · Answer 6 · answered Aug 16 '21 at 12:41

An example of my application can benefit someone:

In the manifest file, my settings are:

<application android:launchMode="singleTask"...>

I use one java class, only as a launcher(it does not show Activity). In the manifest, it is set to:

<activity android:launchMode="singleTop" ...>

Also, other Activities are set the same:

<activity android:launchMode="singleTop" ...>

When a user sends an application to the background, by clicking on the application icon or restoring the application from the background, the last started Activity is returned unchanged, even though they were all started with startActivityForResult() from launcher.

onActivityResult do not fire if launch mode of activity is singleInstance

6 Answers6

Linked