IssueTracker

George, could you please take a look at this? Thanks!

This looks like the same problem as b/334940011 which was fixed by aosp/3146139. Jeremy, can you check to see if it is fixed? There's no repro code in the description, so I'd be shooting in the dark.

Sorry about missing the repro! I retried using ToT animation and still seeing the error. You can use this change which removes all of the workaround logic and adds an dependency on ToT animation to reproduce. Using the Navigation samples in the Compose sample app (I used the Basic Nav Demo but any should work) and cancelling a back gesture will show the behavior.

I'm not seeing any error. I've attached a video.

That is the Navigation Fragment test app. This issue is about the Navigation Compose so you will need to use the compose.integration-tests.demos.

Thanks! I was able to reproduce the problem. As we discussed, the weird fade effect is unfortunately part of the design for interruption. It is a real downside to this design.

I uploaded a change on top of your CL: aosp/3159777 that does a reverse seek when you cancel the predictive back. There are multiple ways to do this and I just chose to use an animate(). You could also do this with a withFrameTimeNanos(). I tried that and it works, but is a few more lines of code and I don't think it is as easy to understand.

Please try this out and see if it solves the issues.

I have a similar issue with canceling Beck Gesture. When I apply Modifier.animateEnterExit to a Composable function inside of one route in NavHost, it doesn't behave as expected and enters the wrong state.

Sample project: https://github.com/erfansn/BackGestureAnimationBug