Fixed
Status Update
No update yet.
Comments
da...@google.com
Hi Ed, Thank you so much for these suggestions. I've been reviewing them and merging them in. Hopefully it should be live. I've included a thank you note too in the article.
il...@google.com
ap...@google.com
Great! Thanks a lot, I'll look for the live updates soon!
jb...@google.com
This has been fixed internally and will be available in the Fragment 1.3.0-beta02 release.
Description
Version used: fragment-ktx:1.3.0-beta01
This bug is part of the problem of
Steps to reproduce
- Fragment1 replaced with fragment2, then press BACK as soon as I see the fragment2 is showing.
- Upon returning, fragment1 calls AnimationInfo.mFocusedView.requestFocus(). However the view being called requestFocus() belongs to the old view tree, it's not belonging to the new view tree that is created during returning.
The bug is hard to reproduce. It's around 1/50 for me using project at
Attached a screenshot showing "detached state" of the view.
The bug is probably not critical because calling requestFocus() on a detached view should be no-op. But it may cause problem if the app added a onFocusChange listener and perform some logic in the fragment (as illustrated in leanback crash