Obsolete
Status Update
Comments
il...@google.com <il...@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.
jb...@google.com <jb...@google.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.
Description
Component used: Fragment Version used: 1.3.0-beta01 Devices/Android versions reproduced on: Samsung S6, API 23
I'm noticing after started using the new FragmentManager implementation, LeakCanary started complaining many times about leaks coming from mAnimationInfo. Unfortunately I only have Leak Canary traces to show.
Once I disable the new FM implementation, I don't see these leaks anymore.