Fragment中动态设置Navigation Graph的最佳实践及状态留存
问题场景与现象
- fragment0内部包含NavHost,通过动态设置导航图实现
fragmentA -> fragmentB -> fragmentC的导航流程;同时fragment0属于更高层级的导航体系,对应流程为fragment0 -> fragment1。 - 从fragment0导航到fragment1后,按返回键回到fragment0,内部NavHost的状态未被保留:原本停留在fragmentB,却重置为导航图的初始页面。
排查原因
当前在onViewCreated回调中动态设置导航图,而从fragment1返回时,fragment0的onViewCreated会再次触发,重新设置导航图的操作覆盖了之前的导航状态,导致状态丢失。
当前代码
override fun onViewCreated(view: View, savedInstanceState: Bundle?) { super.onViewCreated(view, savedInstanceState) val navHostFragment = childFragmentManager.findFragmentById(R.id.nav_host_fragment) as NavHostFragment val navController = navHostFragment.navController val navGraph = navController.navInflater.inflate(R.navigation.nav_of_fragment0) navController.graph = navGraph }
解决方案
核心是仅在Fragment首次初始化时设置导航图,后续重建场景下复用原有状态,推荐两种实现方式:
方案1:通过savedInstanceState判断首次创建
savedInstanceState为null时代表Fragment首次创建,此时执行导航图设置;非null说明是重建(如从上层返回),跳过设置逻辑:
override fun onViewCreated(view: View, savedInstanceState: Bundle?) { super.onViewCreated(view, savedInstanceState) if (savedInstanceState == null) { val navHostFragment = childFragmentManager.findFragmentById(R.id.nav_host_fragment) as NavHostFragment val navController = navHostFragment.navController val navGraph = navController.navInflater.inflate(R.navigation.nav_of_fragment0) navController.graph = navGraph } }
方案2:在onCreate中设置导航图
onCreate生命周期仅在Fragment首次创建时调用一次,后续重建不会重复执行,从根源避免状态被重置:
override fun onCreate(savedInstanceState: Bundle?) { super.onCreate(savedInstanceState) val navHostFragment = childFragmentManager.findFragmentById(R.id.nav_host_fragment) as NavHostFragment? navHostFragment?.let { val navController = it.navController val navGraph = navController.navInflater.inflate(R.navigation.nav_of_fragment0) navController.graph = navGraph } }
额外提示
- 若需根据动态参数切换导航图,可将参数存入Fragment的
arguments,在设置逻辑中增加参数校验,仅当参数变化时重新加载导航图。 - 确保布局中NavHostFragment的
id固定,避免childFragmentManager无法找到实例的问题。
内容的提问来源于stack exchange,提问作者mpountou
相关产品推荐
相关产品推荐

