IssueTracker

Component used: Navigation / NavigationUI Version used: 2.5.2 Devices/Android versions reproduced on: OnePlus 8T / Android 12

I'm using a menu resource file which is bound to a BottomNavigationView. Also I'm setting up the navigation like so NavigationUI.setupWithNavController(bottomNavigationView, navController, false) which means I'm using the experimental version of this API.

I don't want the state of each menu item to be saved since I want to come back to the respective start destination if a BottomNavigationView item gets reselected. So regardless of how deep I got in a navigation graph a reselection of the same item takes you back to the start destination.

I'm using a navGraph which consists of several nested navGraphs like so:

<navigation xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:id="@+id/navigation"
    app:startDestination="@id/destination_one">

    <include app:graph="@navigation/one_navigation" />

    <include app:graph="@navigation/two_navigation" />

    <include app:graph="@navigation/three_navigation" />

    <include app:graph="@navigation/four_navigation" />
</navigation>

The one_navigation could look like this:

<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/destination_one"
    app:startDestination="@id/destination_fragment_one">

    <fragment
        android:id="@+id/destination_fragment_one"
        android:name="com.example.OneFragment"
        android:label="@string/bottom_navigation_one"
        tools:layout="@layout/fragment_one">
    </fragment>
</navigation>

It works pretty good so far, the point is when I click the first BottomNavigationView's menu item N times I got the destination N+1 times on my back stack. If I wanted to leave the app by triggering the system's back navigation I'd have to do it N+1 times.

So I actually expect the startDestination to only exist once on the back stack regardless of how often I click the respective menu item setup with the above mentioned API.