Fixed
Status Update
No update yet.
Comments
lp...@google.com
il...@google.com
It is not possible for the view of the NavHostFragment to be available in the onCreate() of the Activity. In this case, the NavHostFragment lifecycle method follows the Activity lifecycle methods directly therefore, when the activity is on onCreate() so is the NavHostFragment. However, if the Fragment Lifecycle was driven with a LifecycleObserver (https://issuetracker.google.com/issues/127528777 ), onCreate() could be dispatched for a Fragment separately from the onCreate() for an Activity (or a parent Fragment if using a child Fragment). This means that if you were using a LifecycleObserver, it would be possible for the views to be available when onCreate() is dispatched and findNavController() would work in the LifecycleObserver's onCreate().
This is being tracked byhttps://issuetracker.google.com/issues/143145612 .
This is being tracked by
il...@google.com
il...@google.com
Possible workaround #4: call findNavController in onPostCreate.
Description
Version used: 1.1.0-alpha01, 1.1.0-alpha02, 1.1.0-alpha03
Working in: 1.0.0
When a DialogFragment is dismissed by configuration change (i.e rotation), it seems to no longer have access to FragmentManager, and hence its target Fragment.
Attached sample project. To reproduce, rotate the device and it should crash with a null pointer exception as fragment manager is null. Change Fragment dependency to 1.0.0 in build.gradle and then it works fine.