Android基础四大组件——Activity的生命周期，启动模式和应用场景，TaskAffinity，onNewIntent和onSaveInstanceState

一、生命周期

1、onCreate(Bundle saveInstanceState)

* Called when the activity is starting.  This is where most initialization
* should go: calling {@link #setContentView(int)} to inflate the
* activity's UI, using {@link #findViewById} to programmatically interact
* with widgets in the UI, calling
* {@link #managedQuery(android.net.Uri , String[], String, String[], String)} to retrieve
* cursors for data being displayed, etc.

初始化操作，setContentView设置布局资源，findViewById初始化控件UI资源，注意携带的参数saveInstanceState，

* @param savedInstanceState If the activity is being re-initialized after
*     previously being shut down then this Bundle contains the data it most
*     recently supplied in {@link #onSaveInstanceState}.  <b><i>Note: Otherwise it is null.</i></b>

2、onStart( )，用户可见但是没有在前台显示，不可交互

* Called after {@link #onCreate} — or after {@link #onRestart} when
* the activity had been stopped, but is now again being displayed to the
* user.  It will be followed by {@link #onResume}.

3、onResume( )，可以交互，初始化一些资源，如开启动画或者打开相机等消耗CPU的资源

* Called after {@link #onRestoreInstanceState}, {@link #onRestart}, or
* {@link #onPause}, for your activity to start interacting with the user.
* This is a good place to begin animations, open exclusive-access devices
* (such as the camera), etc.
*
* <p>Keep in mind that onResume is not the best indicator that your activity
* is visible to the user; a system window such as the keyguard may be in
* front.  Use {@link #onWindowFocusChanged} to know for certain that your
* activity is visible to the user (for example, to resume a game).

4、onPause( ),做一些数据存储，停止动画和资源回收(如关闭相机)等

* <p>This callback is mostly used for saving any persistent state the
* activity is editing, to present a "edit in place" model to the user and
* making sure nothing is lost if there are not enough resources to start
* the new activity without first killing this one.  This is also a good
* place to do things like stop animations and other things that consume a
* noticeable amount of CPU in order to make the switch to the next activity
* as fast as possible, or to close resources that are exclusive access
* such as the camera.
*
* <p>In situations where the system needs more memory it may kill paused
* processes to reclaim resources.  Because of this, you should be sure
* that all of your state is saved by the time you return from
* this function.  In general {@link #onSaveInstanceState} is used to save
* per-instance state in the activity and this method is used to store
* global persistent data (in content providers, files, etc.)

5、onStop( ),不可见状态

6、onRestart( )，可见状态

7、onDestory( ),不可见，做一些最终的回收工作和资源释放

二、启动模式

根据上面的讲解，并且参考谷歌官方文档，singleInstance的特点可以归结为以下三条：

1. 以singleInstance模式启动的Activity具有全局唯一性，即整个系统中只会存在一个这样的实例
2. 以singleInstance模式启动的Activity具有独占性，即它会独自占用一个任务，被他开启的任何activity都会运行在其他任务中（官方文档上的描述为，singleInstance模式的Activity不允许其他Activity和它共存在一个任务中）
3. 被singleInstance模式的Activity开启的其他activity，能够开启一个新任务，但不一定开启新的任务，也可能在已有的一个任务中开启

应用场景： 

singleTop适合接收通知启动的内容显示页面。例如，某个新闻客户端的新闻内容页面，如果收到10个新闻推送，每次都打开一个新闻内容页面是很烦人的。

singleTask适合作为程序入口点。例如浏览器的主界面。不管从多少个应用启动浏览器，只会启动主界面一次，其余情况都会走onNewIntent，并且会清空主界面上面的其他页面。之前打开过的页面，打开之前的页面就ok，不再新建。

singleInstance适合需要与程序分离开的页面，允许其他程序调用，实现其他程序和我们程序可以共享这个活动的实例。例如闹铃提醒，将闹铃提醒与闹铃设置分离。singleInstance不要用于中间页面，如果用于中间页面，跳转会有问题，比如：A -> B (singleInstance) -> C，完全退出后，在此启动，首先打开的是B。

三、taskAffinity

1、taskAffinity指的是Activity属于哪个task中，一般情况下在同一个应用中，启动的Activity都在同一个Task中。

每个Activity都有taskAffinity属性，这个属性指出了它希望进入的Task。如果一个Activity没有显式的指明taskAffinity，那么它的这个属性就等于Application指明的taskAffinity，如果Application也没有指明，那么该taskAffinity的值就等于应用的包名。

我们可以通过在元素中增加taskAffinity属性来为某一个Activity指定单独的affinity。这个属性的值是一个字符串，可以指定为任意字符串，但是必须至少包含一个”.”，否则会报错。

四、onNewIntent 

Activity的onNewIntent()方法何时会被调用?  

前提:ActivityA已经启动过,处于当前应用的Activity堆栈中; 

当ActivityA的LaunchMode为SingleTop时，如果ActivityA在栈顶,且现在要再启动ActivityA，这时会调用onNewIntent()方法 

当ActivityA的LaunchMode为SingleInstance,SingleTask时,如果已经ActivityA已经在堆栈中，那么此时会调用onNewIntent()方法 

当ActivityA的LaunchMode为Standard时，由于每次启动ActivityA都是启动新的实例，和原来启动的没关系，所以不会调用原来ActivityA的onNewIntent方法

五、onSaveInstance

This method is called before an activity may be killed so that when it comes back some time in the future it can restore its state. For example, if activity B is launched in front of activity A, and at some point activity A is killed to reclaim resources, activity A will have a chance to save the current state of its user interface via this method so that when the user returns to activity A, the state of the user interface can be restored via {@link #onCreate} or {@link #onRestoreInstanceState}.

onSaveInstanceState()方法时在onPause()方法之后onStop()方法之前调用

Android源码解析（二十四）-->onSaveInstanceState执行时机

你后台的Activity被系统回收怎么办？