Android BottomNavigationView 与闪屏返回堆栈问题

发布于 2025-01-09 17:38:36 字数 648 浏览 2 评论 0原文

因此,我使用导航组件库设置了我的 BottomNavigationView (如 此处),一切正常,每个选项卡都可以保留其后堆栈。但是,如果我添加启动屏幕 (Fragment) 并:

  1. 将其设置为起始目标(popUpInclusive 已设置为 true)
  2. SplashFragment 创建操作到第一个选项卡 HomeFragment

然后所有选项卡不再保留其后堆栈,而且导航变得很奇怪:

Splash ->主页(第一个选项卡)->我(第二个选项卡)->首页->按返回,它会返回到“我”,而不是退出应用程序。

PS:我使用带有单个导航图的单个活动模式。

在此处输入图像描述

So I setup my BottomNavigationView (like here) using Navigation Component library and everything works fine, every tab can keep their back stacks. However, if I add a Splash screen (Fragment) and:

  1. Set it as start destination (popUpInclusive set to true already)
  2. Create action from SplashFragment to the first tab HomeFragment

then all the tabs no longer keep their back stacks, plus the navigation becomes weird:

Splash -> Home (first tab) -> Me (second tab) -> Home -> press back, it goes back to Me instead of exiting the app.

PS: I'm using single Activity pattern with single navigation graph.

enter image description here

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

我的奇迹 2025-01-16 17:38:36

好的,感谢 @ianhanniballake,我在这里发布了我的最终解决方案,关键点是 BottomNavigationView 必须是起始目的地,而不是其他 条件目的地,例如登录或启动屏幕。


第 1 步:创建并设置 Splash 布局和片段

  • SplashFragment 添加到导航图中。

  • 无需从 HomeFragment 创建操作 -> SplashFragment,除非你需要过渡动画

步骤 2. 设置 MainViewModel(共享 ViewModel

class MainViewModel : ViewModel() {
    private var _isFirstLaunch = true  //replace with the real condition in the future

    val isFirstLaunch: Boolean         //will be accessed by SplashFragment and HomeFragment
        get() = _isFirstLaunch

    fun updateIsFirstLaunch(isFirstLaunch: Boolean) {
        _isFirstLaunch = isFirstLaunch
    }
}

步骤 3.设置 HomeFragment

class HomeFragment : Fragment() {
    private lateinit var binding: FragmentHomeBinding
    private lateinit var mainViewModel: MainViewModel  //shared ViewModel

    override fun onCreateView(inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle?): View {
        binding = DataBindingUtil.inflate(inflater, R.layout.fragment_home, container, false)
        mainViewModel = ViewModelProvider(requireActivity()).get(MainViewModel::class.java)

        if (mainViewModel.isFirstLaunch) {
            findNavController().navigate(R.id.splashFragment)   //no need action, unless you want transition animation
        }

        binding.goButton.setOnClickListener {
            findNavController().navigate(R.id.action_homeFragment_to_home2Fragment)
        }

        return binding.root
    }
}

第 4 步。设置 SplashFragment

class SplashFragment : Fragment() {
    private lateinit var binding: FragmentSplashBinding
    private lateinit var mainViewModel: MainViewModel  //shared ViewModel

    override fun onCreateView(inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle?): View {
        binding = DataBindingUtil.inflate(inflater, R.layout.fragment_splash, container, false)
        mainViewModel = ViewModelProvider(requireActivity()).get(MainViewModel::class.java)

        binding.exitSplashButton.setOnClickListener {
            mainViewModel.updateIsFirstLaunch(false)  //update the condition

            findNavController().navigateUp()    //go back to HomeFragment
        } 

        requireActivity().onBackPressedDispatcher.addCallback(viewLifecycleOwner) {
            requireActivity().finish()
        }

        return binding.root
    }
}

演示:https://youtu.be/AxiIsY6BtGg

Ok, thanks to @ianhanniballake, I post my final solution here, the key point is that the BottomNavigationView must be the start destination insead of other conditional destination like login or splash screen.


Step 1. Create and Setup Splash Layout and Fragment

  • Add SplashFragment into Navigation graph.

  • No need to create action from HomeFragment -> SplashFragment, unless you need transition animation

Step 2. Setup MainViewModel (shared ViewModel)

class MainViewModel : ViewModel() {
    private var _isFirstLaunch = true  //replace with the real condition in the future

    val isFirstLaunch: Boolean         //will be accessed by SplashFragment and HomeFragment
        get() = _isFirstLaunch

    fun updateIsFirstLaunch(isFirstLaunch: Boolean) {
        _isFirstLaunch = isFirstLaunch
    }
}

Step 3. Setup HomeFragment

class HomeFragment : Fragment() {
    private lateinit var binding: FragmentHomeBinding
    private lateinit var mainViewModel: MainViewModel  //shared ViewModel

    override fun onCreateView(inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle?): View {
        binding = DataBindingUtil.inflate(inflater, R.layout.fragment_home, container, false)
        mainViewModel = ViewModelProvider(requireActivity()).get(MainViewModel::class.java)

        if (mainViewModel.isFirstLaunch) {
            findNavController().navigate(R.id.splashFragment)   //no need action, unless you want transition animation
        }

        binding.goButton.setOnClickListener {
            findNavController().navigate(R.id.action_homeFragment_to_home2Fragment)
        }

        return binding.root
    }
}

Step 4. Setup SplashFragment

class SplashFragment : Fragment() {
    private lateinit var binding: FragmentSplashBinding
    private lateinit var mainViewModel: MainViewModel  //shared ViewModel

    override fun onCreateView(inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle?): View {
        binding = DataBindingUtil.inflate(inflater, R.layout.fragment_splash, container, false)
        mainViewModel = ViewModelProvider(requireActivity()).get(MainViewModel::class.java)

        binding.exitSplashButton.setOnClickListener {
            mainViewModel.updateIsFirstLaunch(false)  //update the condition

            findNavController().navigateUp()    //go back to HomeFragment
        } 

        requireActivity().onBackPressedDispatcher.addCallback(viewLifecycleOwner) {
            requireActivity().finish()
        }

        return binding.root
    }
}

Demo: https://youtu.be/AxiIsY6BtGg

尝蛊 2025-01-16 17:38:36

我按如下方式解决了这个问题:

创建 2 个导航图:

navigation/splash_nav_graph.xml -(这里可能有一个大图,例如授权流程)。

<?xml version="1.0" encoding="utf-8"?>
<navigation xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools"
    android:id="@+id/splash_nav_graph"
    app:startDestination="@id/splashFragment">

    <fragment
        android:id="@+id/splashFragment"
        android:name="com.example.SplashFragment"
        android:label="SplashFragment"
        tools:layout="@layout/fragment_splash">
    </fragment>
</navigation>

navigation/bottom_nav_graph.xml - 主图 (例如):

<?xml version="1.0" encoding="utf-8"?>
<navigation xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:id="@+id/bottom_nav_graph"
    app:startDestination="@id/home_graph">

    <include app:graph="@navigation/fragment1"/>
    <include app:graph="@navigation/fragment2"/>
    <include app:graph="@navigation/fragment3"/>
    <include app:graph="@navigation/fragment4"/>

</navigation>

activity_main.xml

<ViewGroup>
...    
<androidx.fragment.app.FragmentContainerView
            android:id="@+id/navHost"
            ...
            />
    
    <com.google.android.material.bottomnavigation.BottomNavigationView
            android:id="@+id/bottom_navigation_view"
            android:visibility="gone"
            ...
            />
</ViewGroup>

添加 android:visibility="gone" 以便 BottomNavigationView 在开始时不显示

MainActivity.kt

    class MainActivity : AppCompatActivity() {
       
        private val navController: NavController by lazy {
            val navHostFragment = supportFragmentManager.findFragmentById(R.id.navHost) as NavHostFragment
            navHostFragment.navController
        }
    
    override fun onCreate(savedInstanceState: Bundle?) {
            ...
            if (savedInstanceState == null) {
                navController.setGraph(R.navigation.splash_nav_graph)
            } else {
                startBottomNavigation()
            }
        }
    
    
    fun startBottomNavigation() {
            navController.setGraph(R.navigation.bottom_nav_graph)
        binding.bottomNavigationView.apply {
            isVisible = true
            setupWithNavController(navController)
        }
       
    }
}

然后在 SplashFragment(或splash_nav_graph.xml 中的任何其他片段)中,转到主图:

(requireActivity() as MainActivity).startBottomNavigation()

I solved this problem as follows:

Сreate 2 navigation graphs:

navigation/splash_nav_graph.xml - (there may be a large graph here, for example an authorization flow).

<?xml version="1.0" encoding="utf-8"?>
<navigation xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools"
    android:id="@+id/splash_nav_graph"
    app:startDestination="@id/splashFragment">

    <fragment
        android:id="@+id/splashFragment"
        android:name="com.example.SplashFragment"
        android:label="SplashFragment"
        tools:layout="@layout/fragment_splash">
    </fragment>
</navigation>

navigation/bottom_nav_graph.xml - main graph (by example):

<?xml version="1.0" encoding="utf-8"?>
<navigation xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:id="@+id/bottom_nav_graph"
    app:startDestination="@id/home_graph">

    <include app:graph="@navigation/fragment1"/>
    <include app:graph="@navigation/fragment2"/>
    <include app:graph="@navigation/fragment3"/>
    <include app:graph="@navigation/fragment4"/>

</navigation>

activity_main.xml

<ViewGroup>
...    
<androidx.fragment.app.FragmentContainerView
            android:id="@+id/navHost"
            ...
            />
    
    <com.google.android.material.bottomnavigation.BottomNavigationView
            android:id="@+id/bottom_navigation_view"
            android:visibility="gone"
            ...
            />
</ViewGroup>

add android:visibility="gone" so that BottomNavigationView is not displayed at start

MainActivity.kt

    class MainActivity : AppCompatActivity() {
       
        private val navController: NavController by lazy {
            val navHostFragment = supportFragmentManager.findFragmentById(R.id.navHost) as NavHostFragment
            navHostFragment.navController
        }
    
    override fun onCreate(savedInstanceState: Bundle?) {
            ...
            if (savedInstanceState == null) {
                navController.setGraph(R.navigation.splash_nav_graph)
            } else {
                startBottomNavigation()
            }
        }
    
    
    fun startBottomNavigation() {
            navController.setGraph(R.navigation.bottom_nav_graph)
        binding.bottomNavigationView.apply {
            isVisible = true
            setupWithNavController(navController)
        }
       
    }
}

And then in your SplashFragment (or any other fragment in splash_nav_graph.xml), to go to the main graph:

(requireActivity() as MainActivity).startBottomNavigation()
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文