使用Compose AndroidView复用Fragment时onStart/onResume未触发问题

我用Compose的AndroidView封装了一个FragmentContainer来复用包含Google Maps的Fragment，地图的初始化绑定在Fragment的onStart()和onResume()中：

override fun onStart() {
    super.onStart()
    Timber.d("Chargers Fragment OnStart")
    bi.map.onStart()
}

override fun onResume() {
    super.onResume()
    Timber.d("Chargers Fragment OnResume")
    bi.map.onResume()
}

FragmentContainer的实现代码如下：

@Composable
fun FragmentContainer(
    containerId: Int,
    modifier: Modifier = Modifier,
    fragmentManager: FragmentManager,
    commit: FragmentTransaction.(containerId: Int) -> Unit,
    onFragmentViewCreated: (containerId: Int) -> Unit
) {
    var initialized by rememberSaveable { mutableStateOf(false) }

    AndroidView(
        modifier = modifier,
        factory = { context ->
            FragmentContainerView(context)
                .apply { id = containerId }
        },
        update = { view ->
            if (initialized) {
                fragmentManager.onContainerAvailable(view)
                onFragmentViewCreated(view.id)
            } else {
                fragmentManager.commit { commit(view.id) }
                initialized = true
            }
        }
    )
}

private fun FragmentManager.onContainerAvailable(view: FragmentContainerView) {
    val method = FragmentManager::class.java.getDeclaredMethod(
        "onContainerAvailable",
        FragmentContainerView::class.java
    )
    method.isAccessible = true
    method.invoke(this, view)
}

这个页面是底部导航的一部分，切换到其他页面时Fragment的onPause()完全不触发，返回原页面时也不会调用onStart()或onResume()，导致地图无法正常加载。需要解决生命周期触发的问题，同时请指正实现方向是否有误。

问题根源 #

1. Compose与Fragment生命周期适配缺失：AndroidView默认不会自动将Compose的生命周期传递给内部Fragment，底部导航切换时，Fragment无法感知容器的可见性变化。
2. 私有API调用风险：反射调用onContainerAvailable属于FragmentManager的私有方法，后续Android版本迭代可能被移除或修改，引发兼容性问题。
3. 复用逻辑缺陷：当前实现仅在首次初始化时提交Fragment，后续切换未正确触发生命周期回调，FragmentManager无法感知容器状态变化。

修正方案 #

方案1：官方推荐的生命周期绑定实现 #

放弃自定义FragmentContainer，直接通过AndroidView托管Fragment，并绑定Compose的生命周期Owner：

@Composable
fun MapFragmentContainer(
    fragmentManager: FragmentManager,
    containerId: Int = R.id.map_fragment_container,
    modifier: Modifier = Modifier
) {
    val lifecycleOwner = LocalLifecycleOwner.current
    AndroidView(
        modifier = modifier,
        factory = { context ->
            FragmentContainerView(context).apply {
                id = containerId
                fragmentManager.commitNow {
                    add(containerId, MapFragment())
                }
            }
        },
        update = { view ->
            val fragment = fragmentManager.findFragmentById(containerId) as? MapFragment
            fragment?.let { mapFragment ->
                lifecycleOwner.lifecycle.addObserver(object : DefaultLifecycleObserver {
                    override fun onStart(owner: LifecycleOwner) = mapFragment.onStart()
                    override fun onResume(owner: LifecycleOwner) = mapFragment.onResume()
                    override fun onPause(owner: LifecycleOwner) = mapFragment.onPause()
                    override fun onStop(owner: LifecycleOwner) = mapFragment.onStop()
                    override fun onDestroy(owner: LifecycleOwner) {
                        mapFragment.onDestroy()
                        lifecycleOwner.lifecycle.removeObserver(this)
                    }
                })
            }
        }
    )
}

方案2：使用Jetpack Compose官方FragmentHost组件（1.5+） #

Jetpack Compose 1.5及以上版本提供了ui-fragment库，FragmentHost可自动处理Fragment生命周期与Compose的同步：

// 先添加依赖
// implementation "androidx.compose.ui:ui-fragment:1.5.0"

@Composable
fun MapFragmentHost(
    fragmentManager: FragmentManager,
    modifier: Modifier = Modifier
) {
    FragmentHost(
        fragmentManager = fragmentManager,
        fragment = { MapFragment() },
        modifier = modifier
    )
}

该组件会自动将Compose的生命周期传递给Fragment，底部导航切换时可正确触发onPause()、onStart()等方法。

方案3：修正原有FragmentContainer的生命周期绑定 #

若需保留原有实现，添加DisposableEffect监听Compose生命周期，手动触发Fragment回调：

@Composable
fun FragmentContainer(
    containerId: Int,
    modifier: Modifier = Modifier,
    fragmentManager: FragmentManager,
    commit: FragmentTransaction.(containerId: Int) -> Unit,
    onFragmentViewCreated: (containerId: Int) -> Unit
) {
    var initialized by rememberSaveable { mutableStateOf(false) }
    val lifecycleOwner = LocalLifecycleOwner.current
    val fragment = remember { mutableStateOf<Fragment?>(null) }

    AndroidView(
        modifier = modifier,
        factory = { context ->
            FragmentContainerView(context).apply { id = containerId }
        },
        update = { view ->
            if (!initialized) {
                fragmentManager.commit { commit(view.id) }
                fragment.value = fragmentManager.findFragmentById(view.id)
                onFragmentViewCreated(view.id)
                initialized = true
            }
        }
    )

    // 绑定生命周期
    DisposableEffect(lifecycleOwner.lifecycle, fragment.value) {
        val observer = object : DefaultLifecycleObserver {
            override fun onStart(owner: LifecycleOwner) = fragment.value?.onStart() ?: Unit
            override fun onResume(owner: LifecycleOwner) = fragment.value?.onResume() ?: Unit
            override fun onPause(owner: LifecycleOwner) = fragment.value?.onPause() ?: Unit
            override fun onStop(owner: LifecycleOwner) = fragment.value?.onStop() ?: Unit
        }
        lifecycleOwner.lifecycle.addObserver(observer)
        onDispose { lifecycleOwner.lifecycle.removeObserver(observer) }
    }
}

实现方向指正 #

• 禁用私有API调用：反射调用onContainerAvailable会导致应用在Android版本更新时出现兼容性问题，应彻底避免。
• 优先使用官方组件：官方FragmentHost已处理生命周期适配和兼容性，无需自行实现复杂的Fragment托管逻辑。
• 避免手动触发生命周期：尽量通过LifecycleOwner自动绑定生命周期，确保Fragment与Compose的生命周期同步，减少手动调用引发的状态不一致问题。

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