Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Please include a sample project that reproduces your issue.
jb...@google.com <jb...@google.com> #3
Here is the sample project.
Steps to reproduce:
1. Press on "Search" icon;
2. Write something;
3. Search this text, keyboard will be dismissed;
4. Tap on "Dialog" button;
5. Dissmiss dialog;
With the new 1.5.0 fragment library version text will be cleared in the search box after dismissing dialog.
In the version 1.4.1 and lower text in the search is not clearing and this is correct behaviour.
Please suggest some workarounds or how to fix this issue?
Steps to reproduce:
1. Press on "Search" icon;
2. Write something;
3. Search this text, keyboard will be dismissed;
4. Tap on "Dialog" button;
5. Dissmiss dialog;
With the new 1.5.0 fragment library version text will be cleared in the search box after dismissing dialog.
In the version 1.4.1 and lower text in the search is not clearing and this is correct behaviour.
Please suggest some workarounds or how to fix this issue?
an...@google.com <an...@google.com> #4
Hello, have you checked sample project? I hope it will help find the issue.
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().