前言
关于Activity生命周期回调函数是所有Android开发都熟悉的知识,但是最近在计算当前年活跃的Activity计数时总是出现问题。最后发现是onStop的回调出现了问题,很多时候onStop并没有被回调,居然是因为第二个被启动的Activity在onResume的时候判断数据有问题把自己finish了,第一个Activity直接就重新onResume了。现在来写个简单的Demo验证一下。
Demo编写
首先定义TestActivity1,里面只有一个简单的Button,点击这个Button会打开第二个TestActivity2。TestActivity2里面有一个CheckBox,如果选中就在onResume的时候finish掉TestActivity2,否则就什么都不做。两个测试Activity里面都有各个生命周期函数的回调日志输出。TestActivity1是主启动界面,代码如下:
public class TestActivity1 extends AppCompatActivity {
private static final String TAG = "TestActivity";
private static final boolean DEBUG = LogUtils.isEnabled;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_test1);
if (DEBUG) LogUtils.d(TAG, "[TestActivity1] onCreate()");
findViewById(R.id.button).setOnClickListener(new OnClickListener() {
@Override
public void onClick(View v) {
Intent intent = new Intent(TestActivity1.this, TestActivity2.class);
startActivity(intent);
}
});
}
@Override
protected void onStop() {
super.onStop();
if (DEBUG) LogUtils.d(TAG, "[TestActivity1] onStop()");
}
// 其他生命周期回调
.....
}
TestActivity2的代码如下:
public class TestActivity2 extends AppCompatActivity {
private static final String TAG = "TestActivity";
private static final boolean DEBUG = LogUtils.isEnabled;
private CheckBox checkBox;
private SharedPreferences sharedPreferences;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_test2);
sharedPreferences = getSharedPreferences("share", Context.MODE_PRIVATE);
boolean checked = sharedPreferences.getBoolean("checked", false);
if (DEBUG) LogUtils.d(TAG, "[TestActivity2] onCreate()");
checkBox = (CheckBox) findViewById(R.id.chose);
checkBox.setChecked(checked);
checkBox.setOnCheckedChangeListener(new OnCheckedChangeListener() {
@Override
public void onCheckedChanged(CompoundButton buttonView, boolean isChecked) {
sharedPreferences.edit().putBoolean("checked", isChecked).commit();
}
});
}
@Override
protected void onResume() {
super.onResume();
if (DEBUG) LogUtils.d(TAG, "[TestActivity2] onResume()");
boolean checked = sharedPreferences.getBoolean("checked", false);
if (checked) {
finish();
}
}
// 其他生命周期回调函数
...
}
实验结果
- 首先启动TestActivity1,再点击TestActivity1里的Button按钮,执行的生命周期函数日志如下:
[TestActivity1] onCreate() (TestActivity1.java:19)
[TestActivity1] onStart() (TestActivity1.java:32)
[TestActivity1] onResume() (TestActivity1.java:38)
[TestActivity1] onPause() (TestActivity1.java:44)
[TestActivity2] onCreate() (TestActivity2.java:25)
[TestActivity2] onStart() (TestActivity2.java:39)
[TestActivity2] onResume() (TestActivity2.java:45)
[TestActivity1] onStop() (TestActivity1.java:50)
可以看到Activity1.onCreate => Activity1.onStart => Activity1.onResume => Activity1.onPause => Activity2.onCreate => Activity2.onStart => Activity2.onResume => Activity1.onStop,这种生命周期的顺序符合先启动新Acitivty,再处理旧Activity的逻辑。
- 不选中TestActivity2里的CheckBox直接返回,查看结果如下:
[TestActivity2] onPause() (TestActivity2.java:60)
[TestActivity1] onStart() (TestActivity1.java:32)
[TestActivity1] onResume() (TestActivity1.java:38)
[TestActivity2] onStop() (TestActivity2.java:66)
[TestActivity2] onDestroy() (TestActivity2.java:72)
Activity2.onPause => Activity1.onStart => Activity1.onResume => Activity2.onStop => Activity2.onDestroy,优先启动Activity1,然后再处理Activity2。
- 重新进入TestActivity2并选中ChecckBox然后返回,查看结果如下:
[TestActivity1] onPause() (TestActivity1.java:44)
[TestActivity2] onCreate() (TestActivity2.java:25)
[TestActivity2] onStart() (TestActivity2.java:39)
[TestActivity2] onResume() (TestActivity2.java:45)
[TestActivity2] onPause() (TestActivity2.java:60)
[TestActivity1] onResume() (TestActivity1.java:38)
[TestActivity2] onStop() (TestActivity2.java:66)
[TestActivity2] onDestroy() (TestActivity2.java:72)
可见在Activity2.onResume => (正常Activity1.onStop =>) Activity2.onPause => Activity1.onResume => Activity2.onStop
这条顺序少了Activity1.onStop的生命周期回调,这也就是说onStop在新启动的Activity.onResume里finish的时候不会被回调,所以一定要求被执行的动作都要放到onPause中执行。
总结
Activity生命周期对绝大多数Android开发都是很简单的入门知识,但是里面还是有不少的坑。Android开发中有用onStart和onStop计数来判断当前应用是否在前台的逻辑,如果没有处理onResume里finish的情况,很可能导致Activity计数出错,这个问题还是需要在开发中注意。