Android Activity的加载模式和onActivityResult方法之间的冲突

前言

今天在调试程序时，发现在某一Activity上点击返回键会调用该Activity的onActivityResult()方法。我一开始用log，后来用断点跟踪调试半天，还是百思不得其解。因为之前其他的Activity的LaunchMode都是Normal，没有特殊设定，这个Activity由于需求改成了singleTop。直到我确定没有一个地方是代码主动触发的，我才想到了跟Activity的LaunchMode是否有关。

探索

在Google上搜索android activity onactivityresult singTop找到了一些问题。

---

*

*上有些人跟我遇到的问题类似。比如说有一位开发者把Activity设置成了singleTask模式，onActivityResult就收不到任何结果了。当他把singleTask模式改回标准模式，又恢复正常。

这个问题下面给出的答案中，有一位说startActivityForResult的文档中有这么一句话：

For example, if the activity you are launching uses the singleTask launch mode, it will not run in your task and thus you will immediately receive a cancel result.

意思是：比如说，如果你正加载的activity使用了singleTask的加载模式，它不会在你的栈中运行，而且这样你会马上收到一个取消的结果。

即在onActivityResult里马上得到一个RESULT_CANCEL.

他还补充说没有很好的补救方法。可以试试用监听广播的方法。

另一个*的问题中，有人直接回答了不能再singleInstance或singleTop模式下使用startActivityForResult()方法，不仅被采纳了，票数还不低。

剩下的一个*问题中，有人说把singleTask改成singleTop就会正常，得到高达59票并被采纳。实际上我用的就是singTop，可是onActivityResult还是无缘无故被调用了。

---

startActivityForResult的文档：

public void startActivityForResult (Intent intent, int requestCode, Bundle options)

Added in API level 16

Launch an activity for which you would like a result when it finished. When this activity exits, your onActivityResult() method will be called with the given requestCode. Using a negative requestCode is the same as calling startActivity(Intent) (the activity is not launched as a sub-activity).

加载一个Activity，当它结束时你会得到结果。当这个Activty退出了，你的onActivityResult()方法会根据给出的requestCode被调用。使用一个负的requestCode和调用startActivity(intent)一样（activity不被加载成子activity）

Note that this method should only be used with Intent protocols that are defined to return a result. In other protocols (such as ACTION_MAIN or ACTION_VIEW), you may not get the result when you expect. For example, if the activity you are launching uses the singleTask launch mode, it will not run in your task and thus you will immediately receive a cancel result.

注意这个方法只能用于被定义要返回结果的Intent协议。在其他协议中（譬如ACTION_MAIN或ACTION_VIEW），你可能在你想得到结果时得不到。比如，当你正载入的Activity使用的singleTask加载模式，它不会在你的栈中运行，这样你会立马得到一个取消的结果。

As a special case, if you call startActivityForResult() with a requestCode >= 0 during the initial onCreate(Bundle savedInstanceState)/onResume() of your activity, then your window will not be displayed until a result is returned back from the started activity. This is to avoid visible flickering when redirecting to another activity.

有一个特例是，当你在初始的onCreate()方法或onResume()方法中用一个大于等于0的请求码调用startActivityForResult()，你的窗口在被启动的Activity返回结果前不会显示。这是为了避免跳转到另一Activity时可见的闪烁。

This method throws ActivityNotFoundException if there was no Activity found to run the given Intent.

如果运行所给Intent的Activity没被找到，该方法会抛出ActivityNotFoundException异常。

---

Activity的加载模式

Use Cases	Launch Mode	Multiple Instances?	Comments
Normal launches for most activities	"standard"	Yes	Default. The system always creates a new instance of the activity in the target task and routes the intent to it.
	"singleTop"	Conditionally	If an instance of the activity already exists at the top of the target task, the system routes the intent to that instance through a call to itsonNewIntent() method, rather than creating a new instance of the activity.
Specialized launches (not recommended for general use)	"singleTask"	No	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 itsonNewIntent() method, rather than creating a new one.
	"singleInstance"	No	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.

singleTop模式，可用来解决栈顶多个重复相同的Activity的问题。

singleTask模式和后面的singleInstance模式都是只创建一个实例的。

当intent到来，需要创建singleTask模式Activity的时候，系统会检查栈里面是否已经有该Activity的实例。如果有直接将intent发送给它。

singleInstance模式解决了这个问题（绕了这么半天才说到正题）。让这个模式下的Activity单独在一个task栈中。这个栈只有一个Activity。导游应用和google地图应用发送的intent都由这个Activity接收和展示。

总结

后来我改变了onActivityResult里面ResultCode为RESULT_OK时刷新界面的具体实现方法，可是onActivityResult还是会自己被调用，只是暂时没触发任何bug，可它还是个定时炸弹啊。

以后在选择Activity的加载模式时，要考虑onActivtyResult方法与之存在冲突。

参考

1. http://*.com/questions/8960072/onactivityresult-with-launchmode-singletask
2. http://developer.android.com/reference/android/app/Activity.html#startActivityForResult%28android.content.Intent,%20int%29
3. http://*.com/questions/7910840/android-startactivityforresult-immediately-triggering-onactivityresult
4. http://*.com/questions/3354955/onactivityresult-called-prematurely