IssueTracker

Can you attach a sample project that reproduces your issue?

I'm experiencing this issue in a commercial non-open source project so I'd have to provide extracted code fragments. The menu file for instance looks similar to this:

<menu>
    <item
        android:id="@+id/destination_one" />

    <item
        android:id="@+id/destination_two" />

    <item
        android:id="@+id/destination_three" />

    <item
        android:id="@+id/destination_four" />
</menu>

The menu item ids match the top level destination ids as for instance destination_one as required by the NavigationUI library.

The xml layout file of the main activity (there is only one activity) looks pretty much like this:

<androidx.coordinatorlayout.widget.CoordinatorLayout>

    <androidx.constraintlayout.widget.ConstraintLayout>

        <androidx.fragment.app.FragmentContainerView
            android:id="@+id/navigation_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/bottom_navigation"
            app:layout_constraintEnd_toEndOf="parent"
            app:layout_constraintStart_toStartOf="parent"
            app:layout_constraintTop_toTopOf="parent"
            app:navGraph="@navigation/main_navigation" />

        <com.google.android.material.bottomnavigation.BottomNavigationView
            android:id="@+id/bottom_navigation"
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
            app:layout_constraintBottom_toBottomOf="parent"
            app:layout_constraintEnd_toEndOf="parent"
            app:layout_constraintStart_toStartOf="parent"
            app:layout_constraintTop_toBottomOf="@id/navigation_host_fragment"
            app:menu="@menu/main_menu" />
    </androidx.constraintlayout.widget.ConstraintLayout>
</androidx.coordinatorlayout.widget.CoordinatorLayout>

The main_navigation is the first navigation graph I posted in the original post. The behavior I described above only affects the first bottomNavigation item which corresponds to the top level navGraph's startDestination.

Yeah, what we're looking for is a full project (i.e., take a brand new project in Android Studio, put your few bits of code in, and make sure your problem reproduces) as there are a lot of little pieces that can make a difference here.

https://github.com/postfixNotation/NavigationUI

Of course the logic of my project is more sophisticated but this reproduces the issue quite well. If you click the first BottomNavigation item N times you need N+1 system back navigation triggers to leave the app.

So first, we plan to get rid of these APIs in the future. The only behavior for NavigationUI will be to always save and restore the state of the back stack. Luckily, NavigationUI is purposely built only on publicly available APIs so you could always copy our code and make your custom adjustments for whatever your desired behavior is.

The source of the bug is here in NavController. Since we are navigating to the graph and the currentDestination is the start destination on the graph their ids don't match and we never actually do the singleTop operation causing multiple of the same destination to be added to the back stack.

We need to add a fix to ensure we take into account the proper destination on our side, but as I mentioned those APIs will go away in the future. So if you wanted to proactively create your own API, you could make your API navigate directly to the start destination instead of the graph. That would allow you to not wait on our release and ensure you always have your desired behavior going forward.

Thanks a lot for your help! I basically removed the first embedded graph by moving the code directly into the topmost navGraph and as you said, navigate directly to the start destination. As far as I can tell, it seems to work now.

This has been fixed internally and will be available in Navigation 2.6.0-alpha05

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.navigation:navigation-common:2.6.0-alpha05
• androidx.navigation:navigation-runtime:2.6.0-alpha05

I'm also having this issue. I have created a repo for showcasing this: https://github.com/BobbyESP/NavigationParcelablesBugReport

In there you will find another case with a Parcelable object. In my case is quite strange since the logcat shows this error:

Process: com.bobbyesp.navigationbugreport, PID: 23169
                                                                                                    kotlinx.serialization.SerializationException: Serializer for class 'Companion' is not found.
                                                                                                    Please ensure that class is marked as '@Serializable' and that the serialization compiler plugin is applied.
                                                                                                    
                                                                                                    	at kotlinx.serialization.internal.Platform_commonKt.serializerNotRegistered(Platform.common.kt:91)
                                                                                                    	at kotlinx.serialization.SerializersKt__SerializersKt.serializer(Serializers.kt:278)
                                                                                                    	at kotlinx.serialization.SerializersKt.serializer(Unknown Source:1)
                                                                                                    	at androidx.navigation.NavGraph.setStartDestination(NavGraph.kt:404)

Re comment#12, your stacktrace isn't clear which startDestination is causing the issue.

But based on your source code, it is your startDestination in UtilitiesNavigation graph because you are not passing in the song arg for your SongInformationPage.

With safe args, you can conveniently pass in starting arguments by passing in a class instance. The arguments will automatically be available within the starting composable.

This means your nested graph should be

navigation<UtilitiesNavigator>(
       startDestination = SongInformationPage(song = ...),
) 

If your startDestination does not contain arguments, then you can pass in either:

@Serializable 
object MyDestination

startDestination = MyDestination

--- OR ---

@Serializable
class MyDestination

startDestination = MyDestination::class

If you have further questions, please file a separate bug so it is easier for other users with the same question to locate the answer.

comment#15 what's the actual exception message? Can you file a separate bug and attach a sample app?