Jetpack Compose中AndroidViewBinding加载Fragment出现视图未找到崩溃

问题场景 #

我通过以下代码在Jetpack Compose中使用AndroidViewBinding加载Fragment：

val fragmentManager = (LocalContext.current as? FragmentActivity)?.supportFragmentManager
AndroidViewBinding(
    modifier = Modifier.fillMaxSize(),
    factory = { inflater, parent, attachToParent ->
        val binding = ConsumerOdrdGoogleMapLayoutBinding.inflate(inflater, parent, attachToParent)
        val consumerOdrdFragment = ConsumerODRDMapFragment.newInstance("test")
        fragmentManager?.beginTransaction()
            ?.replace(binding.consumerSdkFragmentContainer.id, consumerOdrdFragment, TAG)
            ?.commitAllowingStateLoss()
        binding
    }
)

在部分边缘场景下出现如下崩溃，且难以复现：

Fatal Exception: java.lang.IllegalArgumentException: No view found for id 0x7f0900cf (com.app.myapp.staging:id/consumer_sdk_fragment_container) for fragment ConsumerODRDMapFragment{51aa5f7} (3f2e436a-01b1-48a0-a96e-600816efdab8 id=0x7f0900cf tag=ConsumerODRDMapView)
   at androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:513)
   at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:261)
   at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:1840)
   at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:1758)
   at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:1701)
   at androidx.fragment.app.FragmentManager$4.run(FragmentManager.java:488)
   at android.os.Handler.handleCallback(Handler.java:942)
   at android.os.Handler.dispatchMessage(Handler.java:99)
   at android.os.Looper.loopOnce(Looper.java:201)
   at android.os.Looper.loop(Looper.java:288)
   at android.app.ActivityThread.main(ActivityThread.java:7872)
   at java.lang.reflect.Method.invoke(Method.java)
   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)

崩溃原因分析 #

• 事务执行时机过早：在factory方法中直接执行Fragment事务时，容器View可能还未被添加到视图树中，Fragment尝试关联容器时会找不到目标View。
• Compose重组导致重复事务：Compose的重组特性会多次触发AndroidViewBinding的factory方法，重复执行replace事务，在进程恢复或配置变化时，旧Fragment的状态可能与新容器View不匹配。
• 状态丢失后的恢复问题：使用commitAllowingStateLoss会跳过状态检查，当系统恢复Activity状态时，Fragment可能尝试绑定已被销毁的容器View。

解决方案 #

1. 延迟执行事务，确保容器View已加入视图树 #

通过View.post()延迟执行Fragment事务，保证容器View已经被添加到视图层级中：

val fragmentManager = (LocalContext.current as? FragmentActivity)?.supportFragmentManager
AndroidViewBinding(
    modifier = Modifier.fillMaxSize(),
    factory = { inflater, parent, attachToParent ->
        val binding = ConsumerOdrdGoogleMapLayoutBinding.inflate(inflater, parent, attachToParent)
        binding.root.post {
            fragmentManager?.let { fm ->
                // 检查Fragment是否已存在，避免重复添加
                val existingFragment = fm.findFragmentByTag(TAG)
                if (existingFragment == null) {
                    val consumerOdrdFragment = ConsumerODRDMapFragment.newInstance("test")
                    fm.beginTransaction()
                        .replace(binding.consumerSdkFragmentContainer.id, consumerOdrdFragment, TAG)
                        .commit()
                }
            }
        }
        binding
    }
)

2. 利用LaunchedEffect避免重组重复执行事务 #

使用LaunchedEffect确保事务仅在首次组合时执行一次，同时借助AndroidViewBinding的lambda接收者在View初始化完成后操作：

val fragmentManager = (LocalContext.current as? FragmentActivity)?.supportFragmentManager
val containerId = remember { R.id.consumer_sdk_fragment_container }

AndroidViewBinding(
    modifier = Modifier.fillMaxSize(),
    factory = { inflater, parent, attachToParent ->
        ConsumerOdrdGoogleMapLayoutBinding.inflate(inflater, parent, attachToParent)
    }
) {
    LaunchedEffect(Unit) {
        fragmentManager?.let { fm ->
            if (fm.findFragmentByTag(TAG) == null) {
                val consumerOdrdFragment = ConsumerODRDMapFragment.newInstance("test")
                fm.beginTransaction()
                    .replace(containerId, consumerOdrdFragment, TAG)
                    .commit()
            }
        }
    }
}

3. 安全提交事务，避免状态丢失问题 #

替换commitAllowingStateLoss为commit()，并添加状态检查，仅在状态未保存时提交事务：

fragmentManager?.let { fm ->
    if (!fm.isStateSaved) {
        fm.beginTransaction()
            .replace(containerId, consumerOdrdFragment, TAG)
            .commit()
    } else {
        // 状态已保存时，延迟到恢复后执行
        fm.beginTransaction()
            .replace(containerId, consumerOdrdFragment, TAG)
            .commitAllowingStateLoss()
    }
}

4. 使用正确的FragmentManager #

如果是在Fragment中嵌入Compose，应使用childFragmentManager而非supportFragmentManager，避免Fragment层级混乱：

// 在Fragment的Composable函数中
val fragmentManager = remember { childFragmentManager }

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