Fixed
Status Update
No update yet.
Comments
ap...@google.com
Please include a sample project that reproduces your issue.
jb...@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?
Description
The
invoke()method is the only API exposed fromActivityResultRegistry. This used to make since becauseActivityResultLauncherused the kotlininvoke()and invoking the launcher would callinvoke()on the registry. SinceActivityResultLauncherhas moved to usinglaunch()this connection is no longer clear.We should change the
invoke()inActivityResultRegistryto beonLaunch()so it is clear that it is executed once the call tolaunch()is made.