Fixed
Status Update
Comments
cc...@google.com <cc...@google.com> #2
I should add, I never explicitly set setReorderingAllowed to true. The documentation states
The default is false for applications targeting version versions prior to O and true for applications targeting O and later.
I'm not sure how pertinent this is with the support library fragments.Compile SDK and Target SDK versions are both 27.
The default is false for applications targeting version versions prior to O and true for applications targeting O and later.
I'm not sure how pertinent this is with the support library fragments.Compile SDK and Target SDK versions are both 27.
km...@gmail.com <km...@gmail.com> #3
I can confirm that 27.1.0 has this bug. Downgrading to 27.0.2 worked for us (we came from 27.0.2).
It seems to be related to the fade transition, since setting the transition through the setTransition method of the FragmentTransaction results in the same behaviour.
It seems to be related to the fade transition, since setting the transition through the setTransition method of the FragmentTransaction results in the same behaviour.
kk...@google.com <kk...@google.com> #4
I can confirm this too for 27.1.0. Any workaround for this?
ab...@gmail.com <ab...@gmail.com> #5
Seeing the same issue here with '.setTransition(FragmentTransaction.TRANSIT_FRAGMENT_FADE)' on Google Pixel 8.1.0. Attached a video comparing before and after.
My current workaround is to use a different transition such as TRANSIT_FRAGMENT_OPEN. It looks similar enough for me.
My current workaround is to use a different transition such as TRANSIT_FRAGMENT_OPEN. It looks similar enough for me.
ka...@gmail.com <ka...@gmail.com> #6
I also confirm this. Helps only return on 27.0.2
ka...@gmail.com <ka...@gmail.com> #7
I can confirm this bug. Reverting to 27.0.2 helped.
Description