绝大部分的app首页架构均为Tab + Fragment,当程序发生异常自动恢复,或者app长时间处于后台恢复后,Fragment出现重影(重叠)等问题。固然部分不顾及页面层级的小伙伴,每一个Fragment的view都设置了背景,可能就察觉不出来,可是并不表明没有。而后不少Fragment里面又还有Fragment的使用不当甚至会出现白屏的现象。bash
Activity在非正常退出(点返回等属于正常退出)会调用 onSaveInstanceState 方法来保存数据,其中就包括视图层(View Hierarchy),当该Activity在此被重建时,会调用onRestoreInstanceState方法,以前被实例化过的 Fragment 依然会出如今 Activity 中,而后按照正常生命流程走,在onCreate中FragmentTransaction至关于又再次 add 了 fragment 进去的,hide()和show()方法对以前保存的fragment已经失效了。综上这些因素致使了多个Fragment重叠在一块儿架构
若是savedInstanceState不为null,说明该Activity有保存的实例,在add fragment 时添加标签,具体看源码 selectedFragment方法 其中XXX.getClass().getSimpleName()为Tag 为演示才这样写的app
private void selectedFragment(int position) {
mPosition = position;
FragmentTransaction transaction = getSupportFragmentManager().beginTransaction();
hideFragment(transaction);
switch (position) {
case 0:
if (fragment1 == null) {
fragment1 = new Fragment1();
transaction.add(R.id.fl_content, fragment1,fragment1.getClass().getSimpleName());
} else {
transaction.show(fragment1);
}
break;
case 1:
if (fragment2 == null) {
fragment2 = new Fragment2();
transaction.add(R.id.fl_content, fragment2,fragment2.getClass().getSimpleName());
} else {
transaction.show(fragment2);
}
break;
case 2:
if (fragment3 == null) {
fragment3 = new Fragment3();
transaction.add(R.id.fl_content, fragment3,fragment3.getClass().getSimpleName());
} else {
transaction.show(fragment3);
}
break;
case 3:
if (fragment4 == null) {
fragment4 = new Fragment4();
transaction.add(R.id.fl_content, fragment4,fragment4.getClass().getSimpleName());
} else {
transaction.show(fragment4);
}
break;
default:
}
transaction.commitAllowingStateLoss();
}
复制代码
onCreate方法代码ide
@Override
protected void onCreate(Bundle savedInstanceState) {
super.initData(savedInstanceState);
//不为null,说明是死而复活,移除已经存在的fragment
if (savedInstanceState != null) {
FragmentTransaction mTransaction = getSupportFragmentManager().beginTransaction();
mTransaction.remove(mManager.findFragmentByTag(Fragment4.class.getSimpleName()));
mTransaction.remove(mManager.findFragmentByTag(Fragment3.class.getSimpleName()));
mTransaction.remove(mManager.findFragmentByTag(Fragment2.class.getSimpleName()));
mTransaction.remove(mManager.findFragmentByTag(Fragment1.class.getSimpleName()));
mTransaction.commitAllowingStateLoss();
}
selectedFragment(mPosition);
......
}
复制代码
无需为Fragment 添加Tag 保持最开始的实现逻辑不动 源码ui
**
* 原理 去除Super 切断原有恢复逻辑 保存位置
* @param outState
*/
@SuppressLint("MissingSuperCall")
@Override
protected void onSaveInstanceState(Bundle outState) {
/* 记录当前的position */
outState.putInt("position", mPosition);
}
@Override
protected void onRestoreInstanceState(Bundle savedInstanceState) {
super.onRestoreInstanceState(savedInstanceState);
mPosition = savedInstanceState.getInt("position");
selectedFragment(mPosition);
}
复制代码
当Fragment里面嵌套Fragment时,没有使用getChildFragmentManager(),在Activity恢复后没法获取FragmentManager内的Fragment,从而出现白屏。spa
Fragment嵌套Fragment时,使用getChildFragmentManager()获取事务调试