Android - startActivityForResult immediately triggering onActivityResult

Question

I am launching activities from the main activity in my app using the call startActivityForResult(intent, ACTIVITY_TYPE), and they are all working but one.

This one, when called, launches the activity as desired, but in the log I can see that onActivityResult() is immediately being triggered. The activity shows up but RESULT_CANCELED is immediately returned to onActivityResult().

I then interact with the activity, press a button which calls finish(), and onActivityResult() is not called this time (because apparently a result has already been returned).

Does this make sense to anyone? Has anyone seen this behavior before?

score 323 · Accepted Answer · edited Mar 16 '17 at 17:07

323

You can't use startActivityForResult() if your activity is being launched as a singleInstance or singleTask. standard or singleTop launch mode will fix the problem.

edited Mar 16 '17 at 17:07

stkent

19,772
14
85
111

answered Oct 27 '11 at 01:50

Falmarri

47,727
41
151
191

20

`singleTop` seems fine for me, `singleTask` however was causing this issue and hence `singleInstance` would definitely do too – darnmason Jun 18 '13 at 13:39
6

In my case, did not defined any class as an singleInstance or singleTop, but still it is happening...any suggestion ? – CoDe Aug 27 '14 at 14:42
Note that if the `intent-filter` on the target activity marks it as category `LAUNCHER`, the activity is launched in a new task by default. This can cause the immediately-canceled behavior, even if it is not marked `singleTask` or `singleInstance`. – Alex Jordan Sep 15 '16 at 19:16

score 124 · Answer 2 · edited Jan 14 '19 at 11:37

124

Additionally make sure the intent does not have the Intent.FLAG_ACTIVITY_NEW_TASK set.

From the docs:

This flag can not be used when the caller is requesting a result from the activity being launched.

edited Jan 14 '19 at 11:37

Vadim Kotov

8,084
8
48
62

answered Jan 31 '13 at 22:59

James Zhang

1,709
1
13
8

3

This fixed the problem in my case. The problem was not caused by singleInstance, singleTop nor singleTask. – Diana Dec 04 '13 at 16:16
@Diana, do you remember what you used instead of `Intent.FLAG_ACTIVITY_NEW_TASK` ? – Keselme Aug 06 '19 at 09:05
@Keselme Sorry, it's been a long time, I wish I could help but I don't remember and I can't access that code any more. – Diana Aug 06 '19 at 15:33
Yes, fixed it. startActivityForResult should not be used with Intent.FLAG_ACTIVITY_NEW_TASK – hanilozmen Jun 15 '20 at 08:58
@hanilozmen what is the intent flag you used. I am having the same issue with gps launcher – SVG May 29 '23 at 04:49

score 21 · Answer 3 · edited Jun 15 '16 at 19:10

21

I have seen this behavior before, please make sure your destnation activity (that special activity) is not singleInstance in AndroidManifest file. If the Activity is singleInstance, then it will return RESULT_CANCELED before launched!

edited Jun 15 '16 at 19:10

naXa stands with Ukraine

35,493
19
190
259

answered Oct 27 '11 at 01:58

pangcong

211
1
2

score 20 · Answer 4 · answered Jun 19 '14 at 17:06

20

I'd also like to add that you could call an external app with:
Intent in = caller.getPackageManager().getLaunchIntentForPackage("com.your.package.here");
Which would create an intent with Intent.FLAG_ACTIVITY_NEW_TASK added by default, so call:
in.setFlags(0);
Which will clear that flag, and then you can proceed to: startActivityForResult(in, action);

Reason I'm doing this is that I have a utility app that has common functionality between a few other apps and I can keep the code changes to one location instead of worrying about multiple updates.

answered Jun 19 '14 at 17:06

giannileuani

442
4
9

I know this is old, but this was so absolutely invaluable to me that I wanted to say thanks to the user, and point out for anyone jumping between activities that this is freaking gold! Saved my ass during a hackathon ;) – Wes Winn Sep 26 '14 at 18:35
This is what needs more attention. It is the best solution and works perfectly for me. You saved me a lot of time, thank you so much. – Aritra Roy Aug 25 '15 at 05:22
Up-voting this answer as this was the exact issue I was having this morning! Thanks for the solution! – Will Johnson Apr 07 '17 at 08:43
Thanks. intent.setFlags(0) solved the problem. Now the second app starts ok and returns result to the calling app – Niaz Dec 02 '17 at 14:45

score 5 · Answer 5 · answered Sep 21 '17 at 19:28

5

startActivityForResult() doesn't work with a singleInstance or singleTask activity in pre-lollipop version of Android. Since Android 5 it works (see this answer for more details).

answered Sep 21 '17 at 19:28

noelicus

14,468
3
92
111

score 5 · Answer 6 · answered Sep 22 '17 at 19:49

5

It also triggers if you have FLAG_ACTIVITY_NEW_TASK in your intent.

Intent intent = new Intent(this, MyActivity.class);
intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
startActivityForResult(intent, REQUEST_CODE);

answered Sep 22 '17 at 19:49

Roger Alien

3,040
1
36
46

Thanks. I added FLAG_ACTIVITY_NEW_TASK in my activity. – Chirag Savsani Nov 28 '17 at 13:14

score 1 · Answer 7 · answered Apr 29 '16 at 22:43

1

My problem was with the calling activity. Its declaration in the AndroidManifest had the following property:

android:noHistory="true"

Changed it to "false" and now works fine.

answered Apr 29 '16 at 22:43

user3829751

712
7
20

score 1 · Answer 8 · edited Dec 07 '17 at 12:00

Android 4.4 has a small problem about waiting for the return at the end of the actvity closure To solve this behavior it is important to set :

all activities will have the same task Affinity attribute. (TaskAffinity = "[SAME STRING]")
launchmode=singleTop,
launchIntent.SetFlags(0); // for reset default Intent flags if you launch from package manager

This solution works with all version of Android

See this for taskAffinity: https://asyoulook.com/computers%20&%20internet/android-onactivityresult-being-called-instantly/1004072

score 1 · Answer 9 · answered Nov 26 '18 at 06:35

1

Also, check if android:noHistory="true" on activity in Manifest, if yes, it will not work.

answered Nov 26 '18 at 06:35

Sanju

115
1
13

score 0 · Answer 10 · edited Jun 23 '14 at 13:21

For ActivityGroup or TabHost and others, maybe the xxxActivity is a subActivity of its parent. Then the startActivityForResult can not work but the parent can get the result.

call getParent().startActivityForResult() from your sub-activity
your parent (the ActivityGroup) will be able to handle the onActivityResult. So I created a subclass of ActivityGroup and handled this onActivityResult.
You can re-route that result back to the sub-activity if you need to. Just get the current activity by getLocalActivityManager().getCurrentActivity() . My sub-activities inherit from a custom activity so I added a handleActivityResult(requestCode, resultCode, data) in that subclass for the ActivityGroup to call.

example: http://www.cnblogs.com/relinson/archive/2012/03/25/startActivityForResult.html

What do you think about this special case when calling default web brower : http://www.codeproject.com/Questions/990063/Why-onActivityResult-can-not-catch-result-from-bro?arn=1 — Ahmad Ebrahimi, May 10 '15 at 12:32

score 0 · Answer 11 · edited Jun 15 '16 at 19:09

0

onActivityResult() will also pass RESULT_CANCELED as the resultCode if you misspell the package or class name in the manifest file.

edited Jun 15 '16 at 19:09

naXa stands with Ukraine

35,493
19
190
259

answered May 12 '15 at 02:09

musterjunk

341
3
15

score 0 · Answer 12 · answered Nov 26 '16 at 12:07

0

In Android Manifest set android:launchMode="singleTop" for activity you want open with result and while opening activity set flag intent.setFlags(Intent.FLAG_ACTIVITY_SINGLE_TOP);

answered Nov 26 '16 at 12:07

Krish

616
9
19

score 0 · Answer 13 · answered Sep 11 '18 at 10:31

0

If you defined android:noHistory="true" in the activity in your AndroidManifest.xml, it will cause the same issue here.

answered Sep 11 '18 at 10:31

firemaples

1,521
13
18

Android - startActivityForResult immediately triggering onActivityResult

13 Answers13

Linked