IssueTracker

We are also seeing this issue, affects users in production. Is there a workaround for this?

Other than downgrading to jetpack navigation 2.7 where we don't see this issue (as suggested by someone here: https://issuetracker.google.com/issues/375343407)

I can see the exact same issue, when turning off predictive navigation support in the app, instead of crashing, the component is launching from the wrong place.

When crashing, the stacktrace:

java.lang.IndexOutOfBoundsException: Index -1 out of bounds for length 1

at jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at jdk.internal.util.Preconditions.checkIndex(Preconditions.java:266)
at java.util.Objects.checkIndex(Objects.java:359)
at java.util.ArrayList.get(ArrayList.java:434)
at androidx.navigation.compose.NavHostKt$NavHost$28$1.invokeSuspend(NavHost.kt:611)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108)
at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch(AndroidUiDispatcher.android.kt:81)
at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolineDispatch(AndroidUiDispatcher.android.kt:41)
at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.run(AndroidUiDispatcher.android.kt:57)
at android.os.Handler.handleCallback(Handler.java:958)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:230)
at android.os.Looper.loop(Looper.java:319)
at android.app.ActivityThread.main(ActivityThread.java:9063)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:588)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)

Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [androidx.compose.ui.platform.MotionDurationScaleImpl@af66c29, androidx.compose.runtime.BroadcastFrameClock@96bbae, StandaloneCoroutine{Cancelling}@3f11d4f, AndroidUiDispatcher@eb1bcdc]

After reverting to 2.7 the issue seems resolved, but this version doesn't support predictive back gestures, and the animation system is different too.

It sadly still isn't fixed in 2.9.0-alpha03.

I seen this issues

   if (inPredictiveBack) {
            LaunchedEffect(progress) {
                // This happens in the following line of code
                val previousEntry = currentBackStack[currentBackStack.size - 2]
                transitionState.seekTo(progress, previousEntry)
            }
        } 

Here is this project: MonsterMusic. This problem will occur if you keep clicking on the play page and play queue.

I guess it's because I used this:

  navController.navigate(
                        Router.QueuePage.route
                    ) {
                        popUpTo(Router.MainView.route) {
                            // Inclusive means the start destination is also popped
                            inclusive = false
                        }
                    }

If I use this code, it will quickly come to this problem.

navController.navigate(Router.QueuePage.route) {
 
    popUpTo(Router.QueuePage.route) {
        inclusive = true  
    }
    launchSingleTop = true 
}

I confirm the problem on Samsung S22 14 Android. Any news on its solution?

I've had the same issues, except for me a slow duration isn't required, I've attached another sample project in case it's useful :)

Worth noting that for me it doesn't just happen when navigating backwards, any navigation during a transition causes the old page to remain on screen ( video of it happening in the sample project I attached yesterday attached ).

I got the same issue :

This is a full sample with the full code,

https://github.com/frankois944/kmp-mvvm-exploration/tree/f19b3c3f0260be0367b904d0a5756169b678721b.

Just select an item and got back quickl and look at the logcat, onCleared of the viewmodel is not called.

Yes, b/346608857 has the same issue with predictive back gesture cancellation causing issues in animations. The fix (aosp/3138255) landed in beta04.

Marking this issue as a duplicate.