Android Jetpack Navigation,BottomNavigationView与类似Youtube或Instagram的适当后退导航(片段返回堆栈)?

81

Android Jetpack 导航,使用 BottomNavigationView 自动处理返回按钮点击时的片段回退栈?

我希望实现的功能是,在用户依次选择多个选项卡后,当用户单击“返回”按钮时,应用程序必须重定向到他/她最后打开的页面。

我使用 Android ViewPager 实现了相同的功能,通过在 ArrayList 中保存当前选定的项目。在 Android Jetpack Navigation 发布后是否有任何自动回退栈的功能?我希望使用导航图来实现它。

activity_main.xml

<?xml version="1.0" encoding="utf-8"?>
<android.support.constraint.ConstraintLayout 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/container"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    tools:context=".main.MainActivity">

    <fragment
        android:id="@+id/my_nav_host_fragment"
        android:name="androidx.navigation.fragment.NavHostFragment"
        android:layout_width="match_parent"
        android:layout_height="0dp"
        app:defaultNavHost="true"
        app:layout_constraintBottom_toTopOf="@+id/navigation"
        app:layout_constraintEnd_toEndOf="parent"
        app:layout_constraintStart_toStartOf="parent"
        app:layout_constraintTop_toTopOf="parent"
        app:navGraph="@navigation/nav_graph" />

    <android.support.design.widget.BottomNavigationView
        android:id="@+id/navigation"
        android:layout_width="0dp"
        android:layout_height="wrap_content"
        android:layout_marginStart="0dp"
        android:layout_marginEnd="0dp"
        android:background="?android:attr/windowBackground"
        app:layout_constraintBottom_toBottomOf="parent"
        app:layout_constraintLeft_toLeftOf="parent"
        app:layout_constraintRight_toRightOf="parent"
        app:menu="@menu/navigation" />

</android.support.constraint.ConstraintLayout>

navigation.xml

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

    <item
        android:id="@+id/navigation_home"
        android:icon="@drawable/ic_home"
        android:title="@string/title_home" />

    <item
        android:id="@+id/navigation_people"
        android:icon="@drawable/ic_group"
        android:title="@string/title_people" />

    <item
        android:id="@+id/navigation_organization"
        android:icon="@drawable/ic_organization"
        android:title="@string/title_organization" />

    <item
        android:id="@+id/navigation_business"
        android:icon="@drawable/ic_business"
        android:title="@string/title_business" />

    <item
        android:id="@+id/navigation_tasks"
        android:icon="@drawable/ic_dashboard"
        android:title="@string/title_tasks" />

</menu>
也添加了。
bottomNavigation.setupWithNavController(Navigation.findNavController(this, R.id.my_nav_host_fragment))

我收到了Levi Moreira的一个答案,内容如下:

navigation.setOnNavigationItemSelectedListener {item ->

            onNavDestinationSelected(item, Navigation.findNavController(this, R.id.my_nav_host_fragment))

        }

但是这样做只会导致最后打开的片段实例再次创建。

为BottomNavigationView提供适当的后退导航。


还没有得到答案。 - Bincy Baby
2
略晚地评论一下,但经过一番搜索,我发现当NavOptions不为null时,popBackStack是从NavController.navigate()函数中调用的。我的猜测是目前无法直接实现它。需要自定义NavController的实现,通过反射或类似方法访问mBackStack - HawkPriest
1
如果你给底部导航添加了一个监听器,那么你可以覆盖导航,使其在堆栈中已经包含新的目的地时弹出堆栈,否则执行正常导航。if (!navHost.popBackStack(it.itemId, false)) navHost.navigate(it.itemId) - Marcus Hooper
解决碎片重建问题的一种方法-https://dev59.com/lVUL5IYBdhLWcg3wV22q#51684125 - jL4
我的简单解决方案:https://dev59.com/lVUL5IYBdhLWcg3wV22q#69566457 - KFJK
显示剩余3条评论
14个回答

53
您不需要使用ViewPager来配合BottomNavigation和新的导航架构组件。我一直在使用这两种方式来制作示例应用程序,详情请查看此处链接:https://github.com/Levi-Moreira/TeamManagerApp
基本概念是这样的:您需要一个主活动来托管BottomNavigationView,并且它是导航图的导航主机,这是它的xml外观形式: activity_main.xml
<?xml version="1.0" encoding="utf-8"?>
<android.support.constraint.ConstraintLayout 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/container"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    tools:context=".main.MainActivity">

    <fragment
        android:id="@+id/my_nav_host_fragment"
        android:name="androidx.navigation.fragment.NavHostFragment"
        android:layout_width="match_parent"
        android:layout_height="0dp"
        app:defaultNavHost="true"
        app:layout_constraintBottom_toTopOf="@+id/navigation"
        app:layout_constraintEnd_toEndOf="parent"
        app:layout_constraintStart_toStartOf="parent"
        app:layout_constraintTop_toTopOf="parent"
        app:navGraph="@navigation/nav_graph" />

    <android.support.design.widget.BottomNavigationView
        android:id="@+id/navigation"
        android:layout_width="0dp"
        android:layout_height="wrap_content"
        android:layout_marginStart="0dp"
        android:layout_marginEnd="0dp"
        android:background="?android:attr/windowBackground"
        app:layout_constraintBottom_toBottomOf="parent"
        app:layout_constraintLeft_toLeftOf="parent"
        app:layout_constraintRight_toRightOf="parent"
        app:menu="@menu/navigation" />

</android.support.constraint.ConstraintLayout>

BottomNavigationView 的导航菜单(选项卡菜单)如下所示:

navigation.xml


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

    <item
        android:id="@+id/navigation_home"
        android:icon="@drawable/ic_home"
        android:title="@string/title_home" />

    <item
        android:id="@+id/navigation_people"
        android:icon="@drawable/ic_group"
        android:title="@string/title_people" />

    <item
        android:id="@+id/navigation_organization"
        android:icon="@drawable/ic_organization"
        android:title="@string/title_organization" />

    <item
        android:id="@+id/navigation_business"
        android:icon="@drawable/ic_business"
        android:title="@string/title_business" />

    <item
        android:id="@+id/navigation_tasks"
        android:icon="@drawable/ic_dashboard"
        android:title="@string/title_tasks" />

</menu>

所有这些都只是BottomNavigationView的设置。现在,为了让它与Navigation Arch组件配合使用,您需要进入导航图编辑器,添加所有片段目标(在我的情况下,我有5个选项卡的每一个)并将目标的ID设置为与navigation.xml文件中的名称相同:

输入图像描述

这将告诉Android在选项卡和片段之间建立链接,现在每当用户点击“主页”选项卡时,Android将负责加载正确的片段。 此外,还需要添加一段Kotlin代码到NavHost(即主要活动)中,以使其与BottomNavigationView连接:

您需要在onCreate中添加:

bottomNavigation.setupWithNavController(Navigation.findNavController(this, R.id.my_nav_host_fragment))

这会告诉Android在导航架构组件和BottomNavigationView之间进行连接。有关更多信息,请参见文档

要获得与使用YouTube时相同的行为,请添加以下内容:

navigation.setOnNavigationItemSelectedListener {item ->

            onNavDestinationSelected(item, Navigation.findNavController(this, R.id.my_nav_host_fragment))

        }

这将使目标进入后退堆栈,因此当您点击后退按钮时,最后访问的目标将被弹出。


3
秘诀在于在导航图中添加ID。我正在使用导航抽屉,但原理是相同的。 - JamesSugrue
48
这个在使用返回按钮时很好用。但是如果用户点击底部标签,它不会还原该标签之前打开的子片段(如果有的话)。每次用户点击底部标签时,它都只会打开(父)片段的新实例。因此,如果多次使用底部标签进行导航,这种方式将导致用户感到困惑和沮丧的导航体验。这是一种危险的实现。 - Niroshan
2
没有最大数量限制,但是Material Design规则规定最多只能有5个标签页。 - Levi Moreira
12
当用户切换底部标签时,我不想再次创建碎片,该如何实现?也就是说,我不想在用户每次切换片段时再次发起 API 调用。 - kondal
3
基本上,目前有一个官方解决方法,直到问题得到修复。您可以在这里找到它:https://github.com/android/architecture-components-samples/blob/master/NavigationAdvancedSample/app/src/main/java/com/example/android/navigationadvancedsample/NavigationExtensions.kt - Vaios
显示剩余11条评论

41

你需要像以下的xml一样设置主机导航:

<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:orientation="vertical">

    <android.support.v7.widget.Toolbar
        android:id="@+id/toolbar"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:background="@color/colorPrimary" />

    <fragment
        android:id="@+id/navigation_host_fragment"
        android:name="androidx.navigation.fragment.NavHostFragment"
        android:layout_width="match_parent"
        android:layout_height="0dp"
        android:layout_weight="1"
        app:defaultNavHost="true"
        app:navGraph="@navigation/nav_graph" />

    <android.support.design.widget.BottomNavigationView
        android:id="@+id/bottom_navigation_view"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        app:itemIconTint="@drawable/color_state_list"
        app:itemTextColor="@drawable/color_state_list"
        app:menu="@menu/menu_bottom_navigation" />
</LinearLayout>

使用导航控制器进行设置:

NavHostFragment navHostFragment = (NavHostFragment) getSupportFragmentManager().findFragmentById(R.id.navigation_host_fragment);
NavigationUI.setupWithNavController(bottomNavigationView, navHostFragment.getNavController());

menu_bottom_navigation.xml :

<?xml version="1.0" encoding="utf-8"?>
<menu xmlns:android="http://schemas.android.com/apk/res/android">
    <item
        android:id="@id/tab1"  // Id of navigation graph 
        android:icon="@mipmap/ic_launcher"
        android:title="@string/tab1" />
    <item
        android:id="@id/tab2" // Id of navigation graph
        android:icon="@mipmap/ic_launcher"
        android:title="@string/tab2" />

    <item
        android:id="@id/tab3" // Id of navigation graph
        android:icon="@mipmap/ic_launcher"
        android:title="@string/tab3" />
</menu>

nav_graph.xml:

<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/nav_graph"
    app:startDestination="@id/tab1">
    <fragment
        android:id="@+id/tab1"
        android:name="com.navigationsample.Tab1Fragment"
        android:label="@string/tab1"
        tools:layout="@layout/fragment_tab_1" />

    <fragment
        android:id="@+id/tab2"
        android:name="com.navigationsample.Tab2Fragment"
        android:label="@string/tab2"
        tools:layout="@layout/fragment_tab_2"/>

    <fragment
        android:id="@+id/tab3"
        android:name="com.simform.navigationsample.Tab3Fragment"
        android:label="@string/tab3"
        tools:layout="@layout/fragment_tab_3"/>
</navigation>

如果将“nav_graph”的id设置为“menu_bottom_navigation”,则可以处理底部导航栏的单击。

您可以使用action标签中的popUpTo属性来处理返回操作。enter image description here


你能详细说明一下 popUpTo 的用法吗? - Bincy Baby
3
但是如何设置popUpTo以使其立即返回到之前按下的片段呢?比如,如果您在frag1中进入了frag2,然后进入frag3,按下返回按钮应该返回到frag2。如果您直接从frag1进入frag3,则按下返回按钮应返回到frag1。 popUpTo似乎只能让你选择一个片段来独立返回,而不考虑用户路径。 - Allan Veloso
6
不保留后台堆栈顺序,返回按钮跳到除第二个选项卡外的第一个选项卡。而且不仅如此,还不会保留片段状态,每次点击底部导航项时都会创建新的实例。 - Farid
1
@Farid 可以控制在选择时不每次创建新实例。 - Sohail Zahid
如果我按返回按钮会怎么样?片段将会导航到上一个页面,但是底部导航栏不会被更新。 - Nouman Ch
显示剩余4条评论

28

首先,让我澄清一下Youtube和Instagram如何处理片段导航。

  • 当用户在详细信息片段上时,单击返回或向上按钮会将堆栈弹出一次,并正确地还原状态。对已选的底部栏项进行第二次单击,将弹出整个堆栈到根,并刷新它
  • 当用户在根片段上时,返回会到达底部栏上最后选择的菜单,显示上一个详细信息片段,状态得到适当恢复(JetPack不支持)
  • 当用户在起始目标片段上时,返回会结束活动

以上所有答案都不能使用JetPack导航解决所有这些问题。

JetPack导航没有标准的方法来做到这一点,我发现更简单的方法是将导航xml图分成每个底部导航项目一个,使用Activity FragmentManager处理导航项之间的返回堆栈,在root和detail片段之间使用JetPack NavController处理内部导航(其实现使用childFragmentManager stack)。

假设您的navigation文件夹中有这3个xml:

res/navigation/
    navigation_feed.xml
    navigation_explore.xml
    navigation_profile.xml
将导航 XML 中的 destinationIds 与底部导航栏菜单 ID 相同。此外,对于每个 XML,将 app:startDestination 设置为您想要作为导航项根的片段。创建一个名为 BottomNavController.kt 的类。
class BottomNavController(
        val context: Context,
        @IdRes val containerId: Int,
        @IdRes val appStartDestinationId: Int
) {
    private val navigationBackStack = BackStack.of(appStartDestinationId)
    lateinit var activity: Activity
    lateinit var fragmentManager: FragmentManager
    private var listener: OnNavigationItemChanged? = null
    private var navGraphProvider: NavGraphProvider? = null

    interface OnNavigationItemChanged {
        fun onItemChanged(itemId: Int)
    }

    interface NavGraphProvider {
        @NavigationRes
        fun getNavGraphId(itemId: Int): Int
    }

    init {
        var ctx = context
        while (ctx is ContextWrapper) {
            if (ctx is Activity) {
                activity = ctx
                fragmentManager = (activity as FragmentActivity).supportFragmentManager
                break
            }
            ctx = ctx.baseContext
        }
    }

    fun setOnItemNavigationChanged(listener: (itemId: Int) -> Unit) {
        this.listener = object : OnNavigationItemChanged {
            override fun onItemChanged(itemId: Int) {
                listener.invoke(itemId)
            }
        }
    }

    fun setNavGraphProvider(provider: NavGraphProvider) {
        navGraphProvider = provider
    }

    fun onNavigationItemReselected(item: MenuItem) {
        // If the user press a second time the navigation button, we pop the back stack to the root
        activity.findNavController(containerId).popBackStack(item.itemId, false)
    }

    fun onNavigationItemSelected(itemId: Int = navigationBackStack.last()): Boolean {

        // Replace fragment representing a navigation item
        val fragment = fragmentManager.findFragmentByTag(itemId.toString())
                ?: NavHostFragment.create(navGraphProvider?.getNavGraphId(itemId)
                        ?: throw RuntimeException("You need to set up a NavGraphProvider with " +
                                "BottomNavController#setNavGraphProvider")
                )
        fragmentManager.beginTransaction()
                .setCustomAnimations(
                        R.anim.nav_default_enter_anim,
                        R.anim.nav_default_exit_anim,
                        R.anim.nav_default_pop_enter_anim,
                        R.anim.nav_default_pop_exit_anim
                )
                .replace(containerId, fragment, itemId.toString())
                .addToBackStack(null)
                .commit()

        // Add to back stack
        navigationBackStack.moveLast(itemId)

        listener?.onItemChanged(itemId)

        return true
    }

    fun onBackPressed() {
        val childFragmentManager = fragmentManager.findFragmentById(containerId)!!
                .childFragmentManager
        when {
            // We should always try to go back on the child fragment manager stack before going to
            // the navigation stack. It's important to use the child fragment manager instead of the
            // NavController because if the user change tabs super fast commit of the
            // supportFragmentManager may mess up with the NavController child fragment manager back
            // stack
            childFragmentManager.popBackStackImmediate() -> {
            }
            // Fragment back stack is empty so try to go back on the navigation stack
            navigationBackStack.size > 1 -> {
                // Remove last item from back stack
                navigationBackStack.removeLast()

                // Update the container with new fragment
                onNavigationItemSelected()
            }
            // If the stack has only one and it's not the navigation home we should
            // ensure that the application always leave from startDestination
            navigationBackStack.last() != appStartDestinationId -> {
                navigationBackStack.removeLast()
                navigationBackStack.add(0, appStartDestinationId)
                onNavigationItemSelected()
            }
            // Navigation stack is empty, so finish the activity
            else -> activity.finish()
        }
    }

    private class BackStack : ArrayList<Int>() {
        companion object {
            fun of(vararg elements: Int): BackStack {
                val b = BackStack()
                b.addAll(elements.toTypedArray())
                return b
            }
        }

        fun removeLast() = removeAt(size - 1)
        fun moveLast(item: Int) {
            remove(item)
            add(item)
        }
    }
}

// Convenience extension to set up the navigation
fun BottomNavigationView.setUpNavigation(bottomNavController: BottomNavController, onReselect: ((menuItem: MenuItem) -> Unit)? = null) {
    setOnNavigationItemSelectedListener {
        bottomNavController.onNavigationItemSelected(it.itemId)
    }
    setOnNavigationItemReselectedListener {
        bottomNavController.onNavigationItemReselected(it)
        onReselect?.invoke(it)
    }
    bottomNavController.setOnItemNavigationChanged { itemId ->
        menu.findItem(itemId).isChecked = true
    }
}

请按照以下方式布局 main.xml:

<androidx.constraintlayout.widget.ConstraintLayout 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:layout_width="match_parent"
    android:layout_height="match_parent">

    <FrameLayout
        android:id="@+id/container"
        android:layout_width="match_parent"
        android:layout_height="0dp"
        app:layout_constraintBottom_toTopOf="@id/bottomNavigationView"
        app:layout_constraintTop_toTopOf="parent" />

    <com.google.android.material.bottomnavigation.BottomNavigationView
        android:id="@+id/bottomNavigationView"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:layout_marginStart="0dp"
        android:layout_marginEnd="0dp"
        app:layout_constraintBottom_toBottomOf="parent"
        app:menu="@menu/navigation" />

</androidx.constraintlayout.widget.ConstraintLayout>

像这样在您的活动中使用:

class MainActivity : AppCompatActivity(),
        BottomNavController.NavGraphProvider  {

    private val navController by lazy(LazyThreadSafetyMode.NONE) {
        Navigation.findNavController(this, R.id.container)
    }

    private val bottomNavController by lazy(LazyThreadSafetyMode.NONE) {
        BottomNavController(this, R.id.container, R.id.navigation_feed)
    }

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.main)

        bottomNavController.setNavGraphProvider(this)
        bottomNavigationView.setUpNavigation(bottomNavController)
        if (savedInstanceState == null) bottomNavController
                .onNavigationItemSelected()

        // do your things...
    }

    override fun getNavGraphId(itemId: Int) = when (itemId) {
        R.id.navigation_feed -> R.navigation.navigation_feed
        R.id.navigation_explore -> R.navigation.navigation_explore
        R.id.navigation_profile -> R.navigation.navigation_profile
        else -> R.navigation.navigation_feed
    }

    override fun onSupportNavigateUp(): Boolean = navController
            .navigateUp()

    override fun onBackPressed() = bottomNavController.onBackPressed()
}

这个解决方案看起来不错,但我注意到了一些问题: <FrameLayout /> 应该是 NavHostFragment,每个图形都有自己的默认主页,所以执行 if (savedInstanceState == null) bottomNavController.onNavigationItemSelected() 会触发两次碎片,它不保存碎片状态。 - Sim
保存实例状态的想法完全避免了片段被创建两次。我无法检查这一点,因为最终我扩展了 NavController,并为 NavHostFragment 创建了一个自定义导航器,将其添加到此 NavController 中(我称之为 NavHostFragmentNavController)。然后,我创建了一个名为 navigation_main.xml 的图形,其中包含代表每个底部导航项的 <nav-fragment> 元素。新的实现更大,但使用起来非常简单。代码仍然有一些小错误,我还没有解决。我会在修复它们后发布它。 - Allan Veloso
1
@WWJD,R.id.navigation_feed是一个目的地。我将图形ID命名为与其相同的名称,因为它是初始目的地,因此R.navigation.navigation_feed具有R.id.navigation_feed目的地。 - Allan Veloso
1
抱歉打扰了,我刚刚对那段代码进行了改进,在控制器的初始化中添加了“fragmentManager.addOnBackStackChangedListener”,这样你就可以添加“OnDestinationChangedListener”。这样你就可以始终知道自己在哪个片段中,从而在需要时对Activity UI进行更新。如果需要代码更新,请联系我。再次感谢您的帮助!现在对我来说非常好用。 - jfcogato
1
@AllanVeloso 确定这将是另一种获取它的方式。看起来比我的代码更干净 :) 我会等待你的库!也许我可以用你的更新所有我所做的。顺便说一句,你真的救了我的一天,这个解决方案很好用!我认为我的所有项目现在和将来都将使用这个导航系统! :) - jfcogato
显示剩余7条评论

11

导航库2.4.0没有类似于YouTube、Instagram、Amazon底部导航栏的返回行为。但是它为每个选项卡提供了单独的后退堆栈支持。通过添加更多的代码行,我们可以创建类似于Instagram、Amazon、Youtube的行为。 - Bincy Baby

10

你可以设置带有底部导航视图的ViewPager。ViewPager中的每个片段都将是一个容器片段,它将具有其自己的子片段和后退堆栈。通过这种方式,您可以为ViewPager中的每个选项卡维护后退堆栈。


我曾经使用那种方式,但是应用程序首次启动需要太长时间。 - Bincy Baby
那你肯定做错了什么,确保你没有在片段的oncreate或oncreateview中进行一些繁重的工作。没有任何办法会花费这么长时间。 - Suhaib Roomy
我必须加载内容,我不认为YouTube或Instagram使用ViewPager。 - Bincy Baby
这绝对是一个ViewPager。只需在一页上滚动并尝试切换选项卡,它非常快速,并且会从相同的状态恢复。通过更改同一容器中的片段,您无法实现它,这些是使用ViewPager查看的多个片段。 - Suhaib Roomy
1
我的猜测也是YouTube或Instagram不使用ViewPager。恢复发生的原因是backStack弹出操作,它会恢复最初添加而不是替换的基础片段。 - HawkPriest

6
拥有正确的后退堆栈以保持状态的关键是拥有具有childFragmentManager和自己的后退堆栈的NavHostFragment。Navigation组件的高级示例的扩展文件实际上就是这样做的。
/**
 * Manages the various graphs needed for a [BottomNavigationView].
 *
 * This sample is a workaround until the Navigation Component supports multiple back stacks.
 */
fun BottomNavigationView.setupWithNavController(
    navGraphIds: List<Int>,
    fragmentManager: FragmentManager,
    containerId: Int,
    intent: Intent
): LiveData<NavController> {

    // Map of tags
    val graphIdToTagMap = SparseArray<String>()
    // Result. Mutable live data with the selected controlled
    val selectedNavController = MutableLiveData<NavController>()

    var firstFragmentGraphId = 0

    // First create a NavHostFragment for each NavGraph ID
    navGraphIds.forEachIndexed { index, navGraphId ->
        val fragmentTag = getFragmentTag(index)

        // Find or create the Navigation host fragment
        val navHostFragment = obtainNavHostFragment(
            fragmentManager,
            fragmentTag,
            navGraphId,
            containerId
        )

        // Obtain its id
        val graphId = navHostFragment.navController.graph.id

        if (index == 0) {
            firstFragmentGraphId = graphId
        }

        // Save to the map
        graphIdToTagMap[graphId] = fragmentTag

        // Attach or detach nav host fragment depending on whether it's the selected item.
        if (this.selectedItemId == graphId) {
            // Update livedata with the selected graph
            selectedNavController.value = navHostFragment.navController
            attachNavHostFragment(fragmentManager, navHostFragment, index == 0)
        } else {
            detachNavHostFragment(fragmentManager, navHostFragment)
        }
    }

    // Now connect selecting an item with swapping Fragments
    var selectedItemTag = graphIdToTagMap[this.selectedItemId]
    val firstFragmentTag = graphIdToTagMap[firstFragmentGraphId]
    var isOnFirstFragment = selectedItemTag == firstFragmentTag

    // When a navigation item is selected
    setOnNavigationItemSelectedListener { item ->
        // Don't do anything if the state is state has already been saved.
        if (fragmentManager.isStateSaved) {
            false
        } else {
            val newlySelectedItemTag = graphIdToTagMap[item.itemId]
            if (selectedItemTag != newlySelectedItemTag) {
                // Pop everything above the first fragment (the "fixed start destination")
                fragmentManager.popBackStack(
                    firstFragmentTag,
                    FragmentManager.POP_BACK_STACK_INCLUSIVE
                )
                val selectedFragment = fragmentManager.findFragmentByTag(newlySelectedItemTag)
                        as NavHostFragment

                // Exclude the first fragment tag because it's always in the back stack.
                if (firstFragmentTag != newlySelectedItemTag) {
                    // Commit a transaction that cleans the back stack and adds the first fragment
                    // to it, creating the fixed started destination.
                    fragmentManager.beginTransaction()
                        .attach(selectedFragment)
                        .setPrimaryNavigationFragment(selectedFragment)
                        .apply {
                            // Detach all other Fragments
                            graphIdToTagMap.forEach { _, fragmentTagIter ->
                                if (fragmentTagIter != newlySelectedItemTag) {
                                    detach(fragmentManager.findFragmentByTag(firstFragmentTag)!!)
                                }
                            }
                        }
                        .addToBackStack(firstFragmentTag)
                        .setCustomAnimations(
                            R.anim.nav_default_enter_anim,
                            R.anim.nav_default_exit_anim,
                            R.anim.nav_default_pop_enter_anim,
                            R.anim.nav_default_pop_exit_anim
                        )
                        .setReorderingAllowed(true)
                        .commit()
                }
                selectedItemTag = newlySelectedItemTag
                isOnFirstFragment = selectedItemTag == firstFragmentTag
                selectedNavController.value = selectedFragment.navController
                true
            } else {
                false
            }
        }
    }

    // Optional: on item reselected, pop back stack to the destination of the graph
    setupItemReselected(graphIdToTagMap, fragmentManager)

    // Handle deep link
    setupDeepLinks(navGraphIds, fragmentManager, containerId, intent)

    // Finally, ensure that we update our BottomNavigationView when the back stack changes
    fragmentManager.addOnBackStackChangedListener {
        if (!isOnFirstFragment && !fragmentManager.isOnBackStack(firstFragmentTag)) {
            this.selectedItemId = firstFragmentGraphId
        }

        // Reset the graph if the currentDestination is not valid (happens when the back
        // stack is popped after using the back button).
        selectedNavController.value?.let { controller ->
            if (controller.currentDestination == null) {
                controller.navigate(controller.graph.id)
            }
        }
    }
    return selectedNavController
}

private fun BottomNavigationView.setupDeepLinks(
    navGraphIds: List<Int>,
    fragmentManager: FragmentManager,
    containerId: Int,
    intent: Intent
) {
    navGraphIds.forEachIndexed { index, navGraphId ->
        val fragmentTag = getFragmentTag(index)

        // Find or create the Navigation host fragment
        val navHostFragment = obtainNavHostFragment(
            fragmentManager,
            fragmentTag,
            navGraphId,
            containerId
        )
        // Handle Intent
        if (navHostFragment.navController.handleDeepLink(intent)
            && selectedItemId != navHostFragment.navController.graph.id
        ) {
            this.selectedItemId = navHostFragment.navController.graph.id
        }
    }
}

private fun BottomNavigationView.setupItemReselected(
    graphIdToTagMap: SparseArray<String>,
    fragmentManager: FragmentManager
) {
    setOnNavigationItemReselectedListener { item ->
        val newlySelectedItemTag = graphIdToTagMap[item.itemId]
        val selectedFragment = fragmentManager.findFragmentByTag(newlySelectedItemTag)
                as NavHostFragment
        val navController = selectedFragment.navController
        // Pop the back stack to the start destination of the current navController graph
        navController.popBackStack(
            navController.graph.startDestination, false
        )
    }
}

private fun detachNavHostFragment(
    fragmentManager: FragmentManager,
    navHostFragment: NavHostFragment
) {
    fragmentManager.beginTransaction()
        .detach(navHostFragment)
        .commitNow()
}

private fun attachNavHostFragment(
    fragmentManager: FragmentManager,
    navHostFragment: NavHostFragment,
    isPrimaryNavFragment: Boolean
) {
    fragmentManager.beginTransaction()
        .attach(navHostFragment)
        .apply {
            if (isPrimaryNavFragment) {
                setPrimaryNavigationFragment(navHostFragment)
            }
        }
        .commitNow()

}

private fun obtainNavHostFragment(
    fragmentManager: FragmentManager,
    fragmentTag: String,
    navGraphId: Int,
    containerId: Int
): NavHostFragment {
    // If the Nav Host fragment exists, return it
    val existingFragment = fragmentManager.findFragmentByTag(fragmentTag) as NavHostFragment?
    existingFragment?.let { return it }

    // Otherwise, create it and return it.
    val navHostFragment = NavHostFragment.create(navGraphId)
    fragmentManager.beginTransaction()
        .add(containerId, navHostFragment, fragmentTag)
        .commitNow()
    return navHostFragment
}

private fun FragmentManager.isOnBackStack(backStackName: String): Boolean {
    val backStackCount = backStackEntryCount
    for (index in 0 until backStackCount) {
        if (getBackStackEntryAt(index).name == backStackName) {
            return true
        }
    }
    return false
}

private fun getFragmentTag(index: Int) = "bottomNavigation#$index"

重要的部分是通过上面的函数获取NavHostFragment,如果在后台堆栈中不存在,则将其添加到后台堆栈中。commitNow是同步的,而commit则不同。

private fun obtainNavHostFragment( fragmentManager: FragmentManager, fragmentTag: String, navGraphId: Int, containerId: Int ): NavHostFragment { // 如果 Nav Host fragment 存在,则返回它 val existingFragment = fragmentManager.findFragmentByTag(fragmentTag) as NavHostFragment? existingFragment?.let { return it }

// Otherwise, create it and return it.
val navHostFragment = NavHostFragment.create(navGraphId)
fragmentManager.beginTransaction()
    .add(containerId, navHostFragment, fragmentTag)
    .commitNow()
return navHostFragment

}

我使用上面的NavigationExtension构建了一个如下所示的导航栏:

BottomNavigationView with Navigation Component

带有嵌套导航。

导航图类似,因此只需添加一个:

nav_graph_home.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/nav_graph_home"
    app:startDestination="@id/homeFragment1">


    <fragment
        android:id="@+id/homeFragment1"
        android:name="com.smarttoolfactory.tutorial5_3navigationui_bottomnavigation_nestednavigation.blankfragment.HomeFragment1"
        android:label="HomeFragment1"
        tools:layout="@layout/fragment_home1">
        <action
            android:id="@+id/action_homeFragment1_to_homeFragment2"
            app:destination="@id/homeFragment2" />
    </fragment>

    <fragment
        android:id="@+id/homeFragment2"
        android:name="com.smarttoolfactory.tutorial5_3navigationui_bottomnavigation_nestednavigation.blankfragment.HomeFragment2"
        android:label="HomeFragment2"
        tools:layout="@layout/fragment_home2">
        <action
            android:id="@+id/action_homeFragment2_to_homeFragment3"
            app:destination="@id/homeFragment3" />
    </fragment>

    <fragment
        android:id="@+id/homeFragment3"
        android:name="com.smarttoolfactory.tutorial5_3navigationui_bottomnavigation_nestednavigation.blankfragment.HomeFragment3"
        android:label="HomeFragment3"
        tools:layout="@layout/fragment_home3" >
        <action
            android:id="@+id/action_homeFragment3_to_homeFragment1"
            app:destination="@id/homeFragment1"
            app:popUpTo="@id/homeFragment1"
            app:popUpToInclusive="true" />
    </fragment>

</navigation>

底部导航菜单

menu_bottom_nav.xml

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

    <item
            android:id="@+id/nav_graph_home"
            android:icon="@drawable/ic_baseline_home_24"
            android:title="Home"/>

    <item
            android:id="@+id/nav_graph_dashboard"
            android:icon="@drawable/ic_baseline_dashboard_24"
            android:title="Dashboard"/>

    <item
            android:id="@+id/nav_graph_notification"
            android:icon="@drawable/ic_baseline_notifications_24"
            android:title="Notification"/>
    
</menu>

包含 FragmentContainerViewBottomNavigationView 的 MainActivity 布局。

activiy_main.xml

<?xml version="1.0" encoding="utf-8"?>
<androidx.constraintlayout.widget.ConstraintLayout 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:layout_width="match_parent"
    android:layout_height="match_parent"
    tools:context=".MainActivity">

    <androidx.fragment.app.FragmentContainerView
        android:id="@+id/nav_host_container"
        android:layout_width="0dp"
        android:layout_height="0dp"
        app:layout_constraintBottom_toTopOf="@+id/bottom_nav"
        app:layout_constraintLeft_toLeftOf="parent"
        app:layout_constraintRight_toRightOf="parent"
        app:layout_constraintTop_toTopOf="parent" />

    <com.google.android.material.bottomnavigation.BottomNavigationView
        android:id="@+id/bottom_nav"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        app:layout_constraintBottom_toBottomOf="parent"
        app:menu="@menu/menu_bottom_nav" />

</androidx.constraintlayout.widget.ConstraintLayout>

MainActivity.kt

class MainActivity : AppCompatActivity() {

    private var currentNavController: LiveData<NavController>? = null

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_main)

        supportFragmentManager.addOnBackStackChangedListener {
            val backStackEntryCount = supportFragmentManager.backStackEntryCount
            val fragments = supportFragmentManager.fragments
            val fragmentCount = fragments.size


            Toast.makeText(
                this,
                "MainActivity backStackEntryCount: $backStackEntryCount, fragmentCount: $fragmentCount, fragments: $fragments",
                Toast.LENGTH_SHORT
            ).show()
        }


        if (savedInstanceState == null) {
            setupBottomNavigationBar()
        } // Else, need to wait for onRestoreInstanceState
    }

    override fun onRestoreInstanceState(savedInstanceState: Bundle?) {
        super.onRestoreInstanceState(savedInstanceState)
        // Now that BottomNavigationBar has restored its instance state
        // and its selectedItemId, we can proceed with setting up the
        // BottomNavigationBar with Navigation
        setupBottomNavigationBar()
    }

    /**
     * Called on first creation and when restoring state.
     */
    private fun setupBottomNavigationBar() {
        val bottomNavigationView = findViewById<BottomNavigationView>(R.id.bottom_nav)

        val navGraphIds = listOf(
            R.navigation.nav_graph_home,
            R.navigation.nav_graph_dashboard,
            R.navigation.nav_graph_notification
        )

        // Setup the bottom navigation view with a list of navigation graphs
        val controller = bottomNavigationView.setupWithNavController(
            navGraphIds = navGraphIds,
            fragmentManager = supportFragmentManager,
            containerId = R.id.nav_host_container,
            intent = intent
        )
        // Whenever the selected controller changes, setup the action bar.
        controller.observe(this, Observer { navController ->
            setupActionBarWithNavController(navController)
        })
        currentNavController = controller
    }

    override fun onSupportNavigateUp(): Boolean {
        return currentNavController?.value?.navigateUp() ?: false
    }
}

片段布局和类是简单的类,所以我跳过了它们。您可以查看我构建的完整示例,或者谷歌的存储库以检查高级导航扩展或其他示例。


你对这个有什么想法吗?https://stackoverflow.com/questions/63052712/nested-fragment-backpress-child-inside-parent-have-problem - Sunil Chaudhary
@SunilChaudhary,如果您查看导航组件的存储库或链接中的扩展函数,您就可以看到它是如何工作的。此存储库中的示例展示了不同的实现方式。 - Thracian
哇,你是个天才。我一直在寻找像这样的导航功能。你有上传这个库到 Github 吗? - RodParedes

4
我已经制作了一个类似的应用程序(尚未在PlayStore上发布),它具有相同的导航功能,可能与Google在其应用程序中的实现不同,但功能是相同的。
该结构涉及我拥有的主要活动,我通过显示/隐藏片段来切换其内容,使用以下方法:
public void switchTo(final Fragment fragment, final String tag /*Each fragment should have a different Tag*/) {

// We compare if the current stack is the current fragment we try to show
if (fragment == getSupportFragmentManager().getPrimaryNavigationFragment()) {
  return;
}

// We need to hide the current showing fragment (primary fragment)
final Fragment currentShowingFragment = getSupportFragmentManager().getPrimaryNavigationFragment();

final FragmentTransaction fragmentTransaction = getSupportFragmentManager().beginTransaction();
if (currentShowingFragment != null) {
  fragmentTransaction.hide(currentShowingFragment);
}

// We try to find that fragment if it was already added before
final Fragment alreadyAddedFragment = getSupportFragmentManager().findFragmentByTag(tag);
if (alreadyAddedFragment != null) {
  // Since its already added before we just set it as primary navigation and show it again
  fragmentTransaction.setPrimaryNavigationFragment(alreadyAddedFragment);
  fragmentTransaction.show(alreadyAddedFragment);
} else {
  // We add the new fragment and then show it
  fragmentTransaction.add(containerId, fragment, tag);
  fragmentTransaction.show(fragment);
  // We set it as the primary navigation to support back stack and back navigation
  fragmentTransaction.setPrimaryNavigationFragment(fragment);
}

fragmentTransaction.commit();
}

3
最佳解决方案是由谷歌团队在他们的存储库中提供的解决方案,返回按钮仍然会将您发送回第一个按钮,但其余的行为是“正常的”... 看起来很奇怪,谷歌甚至在使用它(YouTube,Google Photos等)时仍然没有提供一个好的解决方案,他们说Androidx已经出现了帮助,但看起来我们只能绕过去找到一种解决正常问题的方法。
以下是谷歌存储库的链接,其中他们使用每个按钮的navGraph和底部导航。 https://github.com/android/architecture-components-samples/blob/master/NavigationAdvancedSample/app/src/main/java/com/example/android/navigationadvancedsample/NavigationExtensions.kt 将这个文件复制到您的项目中,并查看它们在项目中如何实现。对于返回按钮的行为,您可以创建自己的堆栈,在onBackPressed上只需在该堆栈上导航即可。

2

使用Kotlin编写简短而优秀的代码,将底部导航项与导航图中的片段连接起来:

原始答案:Original Answer

    val navControl = findNavController( R.id.nav_host_frag_main)
    bottomNavigationView?.setupWithNavController(navControl)

*请注意:底部导航栏的id和导航图中的片段必须具有相同的id。 还要感谢@sanat Answer提供的好解释。

最初的回答


你还应该隐藏BNV的直接子项上的“向上”箭头:setupActionBarWithNavController(navController, AppBarConfiguration.Builder(bottomNavigationView.menu).build()) - rubenwardy

0
如果您有一个包含3个项目对应于3个片段的bottomNavigationViewFragmentAFragmentBFragmentC,其中FragmentA是导航图中的startDestination,那么当您在FragmentBFragmentC上并单击返回时,您将被重定向到FragmentA,这是Google推荐的行为,并且默认情况下已实现。
但是,如果您希望更改此行为,则需要使用ViewPager(如其他答案所建议的),或者手动处理片段backStack和back transactions - 这在某种程度上会削弱导航组件的使用。

3
YouTube、Instagram和Saavn有不同的行为。 - Bincy Baby
没错,没有一种正确或错误的方法,只是关于谷歌默认支持(因此推荐)和你的需求是什么。如果这两者不一致,你需要解决它。 - Husayn Hakeem
1
但问题在于,如果您正在使用JetPack Navigation,则返回堆栈将为空。显然,在处理BottomNavigation单击时,JetPack不会向后堆栈添加任何内容。 - Allan Veloso

网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接