Fixed
Status Update
Comments
il...@google.com <il...@google.com> #2
Please include a sample project that reproduces your issue.
ap...@google.com <ap...@google.com> #3
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 <il...@google.com> #4
Hello, have you checked sample project? I hope it will help find the issue.
tf...@gmail.com <tf...@gmail.com> #5
il...@google.com <il...@google.com> #6
Hello, any update please?
b9...@gmail.com <b9...@gmail.com> #7
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?
il...@google.com <il...@google.com> #8
@7 Check @5 for a workaround.
b9...@gmail.com <b9...@gmail.com> #9
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 <il...@google.com> #10
Hello, any estimate please?
b9...@gmail.com <b9...@gmail.com> #11
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
Component used:
lifecycle-viewmodel-ktx
Version used: 2.3.0
Devices/Android versions reproduced on: Pixel 4 running Android 10
Sample project to trigger the issue:https://github.com/tfcporciuncula/view-tree-owner-bug
You can repro the issue by cloning that repo, running it, and then rotating the screen causing a config change.
This is the code I'm using to create a here ):
ViewModel
in aView
(as you can seeEverything works fine, but the app crashes on orientation change with the following stacktrace:
The crash has a pretty clear cause which is this :
So it seems there's this implicit requirement of having the , which is only a
SavedStateRegistryOwner
also be aViewModelStoreOwner
, and that's not the case for the view when it's in a fragment: itsSavedStateRegistryOwner
is aFragmentViewLifecycleOwner
SavedStateRegistryOwner
and not aViewModelStoreOwner
.It feels like
findViewTreeSavedStateRegistryOwner()
should return the fragment itself (likefindViewTreeSavedStateRegistryOwner()
) instead of theFragmentViewLifecycleOwner
, so this would work. Or am I doing something wrong here?If the view is in an activity everything works fine --
findViewTreeSavedStateRegistryOwner()
returns the activity in this case, which is also aViewModelStoreOwner
so everything is good.