Fixed
Status Update
No update yet.
Comments
il...@google.com
Can you explain your use case?
ch...@google.com
I can explain my one. I have a navhost fragment, where I load a graph with just one instance of a screen of acceptance of terms of use. After the approval of the user I load the real nav graph into the same navhost. According to the documentation The current data of the graph should be reset, so the new Navigation items can be reached. But unfortunately the new items from the graph cannot be reached.
ch...@google.com
Re #3 - that's not how you should be doing conditional navigation (see the documentation: https://developer.android.com/topic/libraries/architecture/navigation/navigation-conditional ), but we should take a closer look at this anyways.
il...@google.com
Any updates on this issue?
Thanks
Thanks
il...@google.com
an...@gmail.com
Navigation now pops all destinations off the back stack (if any exists) when you call setGraph().
This has been fixed internally inhttps://android-review.googlesource.com/867951 and will be available in Navigation 1.0.0-alpha10
This has been fixed internally in
jb...@google.com
li...@gmail.com
@6 Can't confirm. Seems it still exists. Here:
il...@google.com
Re #7 - this is being actively worked on in the
il...@google.com
A postponed fragment will never reach onResume() (part of the contract of a postponed fragment is that it can only go up to STARTED), so the example project needed to be changed to use onStart().
That being said, this has been fixed internally and will be avilable in Fragment 1.3.0-alpha08.
Note: this fix relies on using the
Description
Version used: 2.0.0
The fragment I use as my startDestination uses postponeEnterTransition() and startPostponedEnterTransition() for transition purposes. When my app is opened though, that fragment is never actually visible.
This is because the Fragment does *not* receive onStart() or onResume(), so my data source is never setup, so I do not call scheduleStartPostponedTransitions(). The last lifecycle callback I get is onViewCreated().
If I remove the call to postponeEnterTransition() then everything works as normal, except my transitions.