Flutter Fragment复用异常：视图层级覆盖问题求助

问题概述 #

存在两个可复用Fragment，第二个为Flutter Fragment，出现以下显示异常：

• Android API 29及以上版本：详情Activity出栈后，Flutter Fragment会渲染在第一个Fragment之上
• Android API 29以下版本：Flutter Fragment始终显示在主Activity所有视图最上层

复现代码 #

Fragment切换复用逻辑 #

private void switchTo(String tag) {
    FragmentManager supportFragmentManager = getSupportFragmentManager();
    FragmentTransaction fragmentTransaction = supportFragmentManager.beginTransaction();
    if (tag.equals("home")) {
        fragmentTransaction.show(homeFragment);
        fragmentTransaction.hide(notificationsFragment);
    } else {
        fragmentTransaction.show(notificationsFragment);
        fragmentTransaction.hide(homeFragment);
    }
    fragmentTransaction.commitNowAllowingStateLoss();
}

Flutter Fragment初始化代码 #

public View onCreateView(@NonNull LayoutInflater inflater,
                         ViewGroup container, Bundle savedInstanceState) {
    FragmentManager fragmentManager = getChildFragmentManager();
    if (mRepGoalsFlutterFragment1 == null) {
        mRepGoalsFlutterFragment1 = FlutterFragment.withNewEngine()
                .build();
        fragmentManager
                .beginTransaction()
                .add(R.id.card_view7,
                        mRepGoalsFlutterFragment1,
                        TAG_REP_GOALS_FLUTTER_FRAGMENT_1)
                .commit();
    }

    return inflater.inflate(R.layout.fragment_notifications, container, false);
}

解决方案 #

核心原因 #

Flutter Fragment默认使用SurfaceView渲染，该组件的渲染层级独立于Android常规View体系，直接绘制在Window的Surface之上，不受普通View的visibility属性或Fragment的hide/show方法控制，因此会出现层级穿透问题。

具体修复步骤 #

1. 切换为TextureView渲染模式
   TextureView属于Android View体系的一部分，会遵循正常的视图层级规则。修改Flutter Fragment初始化代码，指定使用TextureView：

mRepGoalsFlutterFragment1 = FlutterFragment.withNewEngine()
        .renderMode(RenderMode.texture) // 强制使用TextureView替代SurfaceView
        .build();

2. 强化Fragment切换时的层级控制
   在切换Fragment时，除了调用hide/show，额外通过控制Fragment根视图的可见性来同步层级状态：

private void switchTo(String tag) {
    FragmentManager supportFragmentManager = getSupportFragmentManager();
    FragmentTransaction fragmentTransaction = supportFragmentManager.beginTransaction();
    if (tag.equals("home")) {
        fragmentTransaction.show(homeFragment);
        fragmentTransaction.hide(notificationsFragment);
        if (notificationsFragment.getView() != null) {
            notificationsFragment.getView().setVisibility(View.GONE);
        }
    } else {
        fragmentTransaction.show(notificationsFragment);
        fragmentTransaction.hide(homeFragment);
        if (notificationsFragment.getView() != null) {
            notificationsFragment.getView().setVisibility(View.VISIBLE);
        }
    }
    fragmentTransaction.commitNowAllowingStateLoss();
}

3. API 29+返回Activity后的层级修正
   在API 29及以上版本，从详情Activity返回主Activity时，手动触发视图树重绘，确保Flutter Fragment回到正确层级：

@Override
protected void onResume() {
    super.onResume();
    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.Q) {
        getWindow().getDecorView().requestLayout();
    }
}

效果验证 #

通过上述修改，Flutter Fragment将完全遵循Android视图层级规则，无论是Fragment切换还是Activity栈操作，都能保持正确的显示层级，解决不同API版本下的异常问题。

内容的提问来源于stack exchange，提问作者chdo