Component used: Fragment 1.3.0-alpha08, Transition 1.3.1 Devices/Android versions reproduced on: Any

This bug is similar to https://issuetracker.google.com/issues/164794529 but is actually a different bug.

I am attaching a sample. As before, it consists of two fragments that uses a shared element transition. When you click on the red box in the first fragment, the transition starts. After half the transition has run, the backstack will be popped and thus the transition is interrupted. In the sample, the transition in the fragment we're returning to doesn't run and so the view jumps to its original position again. However, if you turn off setReorderAllowed on the fragment transaction, the view smoothly transitions back. It appears that if the view is not destroyed and recreated, the transition does not run.

The expected behavior is that the fragment transitions would look and behave the same way even with reorder allowed (which is the recommended value to be used, and necessary if you rely on postponing).