Assigned
Status Update
No update yet.
Comments
si...@google.com
se...@google.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.
ye...@revolut.com
Turns out, we already had a tracking bug for this issue, will follow up on that other one.
Description
Component used: Emoji2 Version used: 1.0.0-beta01 Devices/Android versions reproduced on: n/a, unit test
Repro project:https://github.com/edenman/kmpPlayground/tree/00d11de74adb62e25e67800be49a2511088a4cc8
The test:
https://github.com/edenman/kmpPlayground/blob/00d11de74adb62e25e67800be49a2511088a4cc8/app/src/test/java/chat/quill/util/AndroidEmojiDetectorTest.kt
This test worked in emojiCompat v1 (bundled).