DialogFragmentNavigator does not currently use the new Navigator APIs (i.e. push/popWithTransition). As a result the NavBackStackEntrys associated with the DialogFragment all change Lifecycle.State immediately instead of in sync with the DialogFragment.

This can create problems, for example if a user attempted to access the ViewModel of their NavBackStackEntry as the Dialog was being dismissed, but before it was destroyed, Navigation would crash stating that the entry is not available. It should still be there until the Dialog is actually destroyed.