修改NavGraph起始页后，Monitoring返回Dashboard导航失效问题

1. 修正ID不匹配核心问题 #

你代码里存在ID命名不一致的关键错误：

• NavGraph和抽屉菜单中Fragment的ID是nav_monitoring_fragment、nav_login_fragment、nav_dashboard_fragment
• 但MainActivity的appBarConfiguration里写的是R.id.monitoringFragment等错误ID，导致抽屉菜单无法正确匹配导航目的地

修改MainActivity代码：

class MainActivity : AppCompatActivity() {
    private lateinit var appBarConfiguration: AppBarConfiguration

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        
        appBarConfiguration = AppBarConfiguration(
            setOf(
                R.id.nav_monitoring_fragment, R.id.nav_login_fragment, R.id.nav_dashboard_fragment
            ), binding.drawerLayout
        )
        
        val navController = findNavController(R.id.nav_host_fragment_content_main)
        setupActionBarWithNavController(navController, appBarConfiguration)
        binding.navView.setupWithNavController(navController)
    }
}

2. 完善抽屉菜单配置 #

更新抽屉菜单，添加Dashboard项，确保所有item的ID和NavGraph完全一致：

<?xml version="1.0" encoding="utf-8"?>
<menu xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="http://schemas.android.com/tools"
    tools:showIn="navigation_view">

    <group android:checkableBehavior="single">
        <item
            android:id="@id/nav_monitoring_fragment"
            android:title="@string/drawer_menu_monitoring" />
        <item
            android:id="@id/nav_dashboard_fragment"
            android:title="@string/dashboard" />
        <item
            android:id="@id/nav_login_fragment"
            android:title="@string/drawer_menu_user_mgmt" />
    </group>
</menu>

3. 优化Dashboard到Monitoring的跳转栈逻辑 #

当前按钮跳转只是简单将Monitoring加入栈顶，导致抽屉点击Dashboard时栈混乱。修改NavGraph中的action，添加栈管理配置：

<action
    android:id="@+id/showMonitoringFromDashboard"
    app:destination="@id/nav_monitoring_fragment"
    app:popUpTo="@id/nav_monitoring_fragment"
    app:popUpToInclusive="false"
    app:launchSingleTop="true" />

• app:popUpTo：跳转到Monitoring时，将栈中Monitoring之上的页面弹出
• app:launchSingleTop="true"：避免重复创建Monitoring实例

或者在代码中显式指定导航选项：

binding.btnGotoMonitoring.setOnClickListener {
    val action = DashboardFragmentDirections.showMonitoringFromDashboard()
    val navOptions = NavOptions.Builder()
        .setPopUpTo(R.id.nav_monitoring_fragment, false)
        .setLaunchSingleTop(true)
        .build()
    findNavController().navigate(action, navOptions)
}

4. 修复Login自动跳转与生命周期日志问题 #

确保LoginFragment在正确的生命周期中执行自动跳转逻辑，同时检查日志配置：

override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
    super.onViewCreated(view, savedInstanceState)
    Log.d("LoginFragment", "onViewCreated triggered")
    
    // 读取SharedPreference中的账户信息
    val sharedPref = requireContext().getSharedPreferences("account_prefs", Context.MODE_PRIVATE)
    val accountJson = sharedPref.getString("account", null)
    
    accountJson?.let {
        val account = Gson().fromJson(it, Account::class.java)
        // 跳转到Dashboard并传递账户信息
        findNavController().navigate(LoginFragmentDirections.showDashboard(account))
    }

    // 登录按钮逻辑
    binding.btnLogin.setOnClickListener {
        // 处理登录验证逻辑
        val account = Account(...) // 构造有效账户对象
        // 保存到SharedPreference
        val editor = sharedPref.edit()
        editor.putString("account", Gson().toJson(account))
        editor.apply()
        // 跳转至Dashboard
        findNavController().navigate(LoginFragmentDirections.showDashboard(account))
    }
}

• 若日志未触发，检查Logcat的过滤标签是否正确，确认Fragment是否被正确实例化（比如launchSingleTop会复用已有实例，不会重复调用onCreateView）

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