Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Yigit, do you have time to fix it?
reemission of the same liveData is racy
reemission of the same liveData is racy
an...@google.com <an...@google.com> #4
Thanks for the detailed analysis. This may not be an issue anymore since we've started using Main.immediate there but I' not sure; I'll try to create a test case.
Description
Version used: 1.2.0-rc01
Devices/Android versions reproduced on: all
If your Fragment was added with animations or transitions and you go to remove it via code such as
fragmentManager.commitNow {
remove(fragment)
}
Previously, you could guarantee that fragmentManager.findFragmentById() / findFragmentByTag() would return null.
However, it seems like the Fragment 1.2 changes where onDestroyView() (and hence, onDestroy() / onDetach()) are not called until the animation/transition completes means this is no longer the case.
FragmentManager's state should always be up to date after commitNow(), even if the Fragment itself has not concluded its drive to onDetach().