Obsolete
Status Update
No update yet.
Comments
jb...@google.com
ap...@google.com
Please include a sample project that reproduces your issue.
th...@outlook.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?
Description
Version used: 1.8.0-SNAPSHOT
I've written a test to showcase a bug I encounter in real world usage where sometimes when navigating back using the 'navigate up' back button, the animation is not played and the top fragment remains on top. It seems to happen in combination with a shared element transition and predictive back.
Navigating back from this undefined state triggers a memory leak.
The test is available in the sample project: