Status Update
No update yet.
Comments
jo...@gmail.com
This actually has nothing to do with NavHostFragment, but is the behavior of NavController's setGraph().
When you call navController.setGraph(R.navigation.navigation_graph), it stores that ID and will restore that ID automatically.
If you were to instead use:
NavInflater navInflater = new NavInflater(this, navController.getNavigatorProvider());
navController.setGraph(navInflater.inflate(R.navigation.navigation_graph));
Then NavController would not restore the graph itself and the call to restoreState() you point out would only restore the back stack state, etc. but would wait for you to call setGraph again.
You're right that the inconsistency between the two setGraph methods is concerning. We'll take a look.
When you call navController.setGraph(R.navigation.navigation_graph), it stores that ID and will restore that ID automatically.
If you were to instead use:
NavInflater navInflater = new NavInflater(this, navController.getNavigatorProvider());
navController.setGraph(navInflater.inflate(R.navigation.navigation_graph));
Then NavController would not restore the graph itself and the call to restoreState() you point out would only restore the back stack state, etc. but would wait for you to call setGraph again.
You're right that the inconsistency between the two setGraph methods is concerning. We'll take a look.
pa...@gmail.com
Turns out, we already had a tracking bug for this issue, will follow up on that other one.
Description
When I open the keyboard and then I tap the button to switch to another fragment, the bottomsheet fragment will scroll till reach the top of the recyclerview hiding the top of the bottomsheet view.
It happens just if the EditText is inside of one of the nested fragment and if there is a RecyclerView inside of the BottomSheet.
I've attached a gif with the problem, some files and here there is the link for the project: