Fixed
Status Update
No update yet.
Comments
ap...@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?
ap...@google.com
Hello, have you checked sample project? I hope it will help find the issue.
ap...@google.com
ap...@google.com
Hello, any update please?
ap...@google.com
Hello
I raised similar issue with this ticket
This makes the SearchView unusable/broken when fragments are changed (i.e base on searchView input query)
What can we do to fix this problem? What is the progress of work on solving this problem?
Description
Component used: Fragment Version used: 1.4.0-alpha01
The Fragment StrictMode outputs to the log when you use
penaltyLog()orpenaltyDeath(). While these print the Violation class name and the stack trace, they don't provide useful structured information that would help developers figure out the cause of the exception from only the log message.Building on top of
Violationshould use what structured information it has access to in order to override the exception message with a more useful, pre-formatted log message.We should still keep the currently used 'Policy violation in $fragmentName' message (as the exception message will be included in the output of the violation as the
Exceptionparameter to theLogcall.