Assigned
Status Update
Comments
ei...@salesforce.com <ei...@salesforce.com> #2
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.
ei...@salesforce.com <ei...@salesforce.com> #3
Turns out, we already had a tracking bug for this issue, will follow up on that other one.
se...@google.com <se...@google.com> #4
Thank you for promptly replying to my report. You are right that the issue you've just mentioned is similar to mine. I shall continue observing the progress over there.
ei...@salesforce.com <ei...@salesforce.com> #5
Thanks, Sean! Much appreciated!
se...@google.com <se...@google.com>
se...@google.com <se...@google.com> #6
This won't make 1.4. Evaluating for 1.5.
Description
Version used: 1.5.1
Devices/Android versions reproduced on: Pixel 2, Android 11 (real device)
AppCompatMultiAutoCompleteTextView will not render emoji using EmojiCompat unless explicitly enabled during "init {}"
- API call: