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?
pv...@gmail.com
Hello, have you checked sample project? I hope it will help find the issue.
jb...@google.com
wi...@gmail.com
Hello, any update please?
[Deleted User] <[Deleted User]>
Comment has been deleted.
va...@gmail.com
@7 Check @5 for a workaround.
an...@gmail.com
Hi, i am also facing this issue after we dismiss a DialogFragment, the callback comes in the onPrepareOptionsMenu(), which is causing the issues for me.
Any idea on when it will be fixed?
Any idea on when it will be fixed?
il...@google.com
Hello, any estimate please?
lu...@gmail.com
Facing a similar kind of issue when scrolling the fragments using a ViewPager.
https://issuetracker.google.com/issues/267677504
Can you update regarding any progress on this issue.
Can you update regarding any progress on this issue.
Description
Currently, when using the
ActivityResultRegistry, you can calllaunch()on anActivityResultLauncherthat is not currently registered. This means that the targeted Activity can be launched, but there will not be any result meaning the API is not behaving as intended.Instead of allowing developers to run into this issue, we should always throw from the registry when the launcher is not registered.