Component used: Fragment

Version used: 1.7.0-alpha03

Devices/Android versions reproduced on: Pixel 6 with Android 14

The short summary of the issue is that once the predictive back gesture is completed (or started and canceled only), the fragments seem to be stacked on top of each other, with the top one displaying its contents without being interactive and the bottom one handling the touch input, which leads to crashes and unexpected behavior.

I've attached a minimal sample project to reproduce and describe the issues:

Navigate through the app and its two fragments without using the back gesture: everything works as expected.
On the second fragment, use the back gesture to navigate back to the first fragment. Then tap on the overflow menu: the app crashes unexpectedly with an IndexOutOfBoundsException in FragmentManager.
Relaunch the app and on the second fragment, start the back gesture but cancel it. Then tap on the overflow menu of the second fragment: it doesn't react anymore. Move slightly left with the finger and tap again to open the menu: this time it opens and the toast says "First fragment", which means the touch input is handled by the first fragment and contents are displayed by the second one. Now pause the app by moving it to the background, then resume it: the contents are fully gone and the overflow menu of the first fragment can still be opened by tapping on the top right corner (but slightly left of it because the overflow menu of the second fragment seems to cover the first). Using the back gesture will bring you back to the first fragment, which is then again acting as described in step 2.
Repeat step 3 without pausing the app, then tap on the disabled(!) "Go to second fragment" button of the second fragment: the app crashes with an IllegalArgumentException because the touch input is again handled by the first fragment and it's (enabled!) top button, so the executed navigation transaction (first to second fragment with the second currently displayed) is obviously illegal.

Hope you guys can fix that for the next alpha, thanks for your amazing work! :)