Fixed
Status Update
No update yet.
Comments
il...@google.com
Please include a sample project that reproduces your issue.
ap...@google.com
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?
il...@google.com
an...@google.com
Hello, have you checked sample project? I hope it will help find the issue.
Description
Version used: 1.2.0-rc03
Devices/Android versions reproduced on:
When you use a <fragment> tag and do a configuration change to a layout that does not contain the <fragment> tag, the Fragment is still recreated by FragmentManager, but stays in the INITIALIZING state.
If the FragmentManager is then destroyed (i.e., by the user hitting back, the parent fragment being removed, etc), the non-config state is not correctly cleared out. This can be seen by checking if any ViewModels are cleared or if any retained child fragments are destroyed.