Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Looks like it's related to https://cs.android.com/androidx/platform/frameworks/support/+/d7f5e8294c72d753234ff82e868cd09a06241c5e - When destroying the fragment view, moveToState is called and ends up re-creating the fragment view now that check has been removed
il...@google.com <il...@google.com> #3
Seems like this is already fixed in master as a side effect of
You'd want to add the snapshot repository to your repositories
block:
maven {
url "https://ci.android/com/builds/submitted/6080026/androidx_snapshot/latest/repository/"
}
then switch to androidx.fragment:fragment-ktx:1.3.0-SNAPSHOT
.
We'll look into cherry picking the changes into Fragment 1.2.0
da...@gmail.com <da...@gmail.com> #4
I can confirm that the issue appears to be fixed in that snapshot. Thanks!
Description
Version used: 1.1.0-alpha05
FragmentManager unconditionally changes the View's layer type to View.LAYER_TYPE_HARDWARE, resetting it to LAYER_TYPE_NONE when the animation is over. We shouldn't change the layer type at all (and it is totally unnecessary on reasonably modern devices) and leave the decision of layer type to users.