Fixed
Status Update
Comments
il...@google.com <il...@google.com> #2
This is affecting CameraView as well.
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #3
Bugjuggler: wait until next quarter
il...@google.com <il...@google.com> #4
Hi. I've received your bug and will wait until 2020-01-01 00:00 -0800 PST and then assign the bug to ericng@google.com.
ru...@gmail.com <ru...@gmail.com> #5
Hello,
A fix has been applied for most cases in Alpha08 (Dec 18th release), however we are keeping this open for a more robust fix to come. Thanks.
A fix has been applied for most cases in Alpha08 (Dec 18th release), however we are keeping this open for a more robust fix to come. Thanks.
il...@google.com <il...@google.com>
il...@google.com <il...@google.com>
il...@google.com <il...@google.com> #8
Hi. I've received your bug and will wait for b/146048690 to be fixed and then assign the bug to ericng@google.com.
[Deleted User] <[Deleted User]> #9
Bugjuggler: wait until next month
ap...@google.com <ap...@google.com> #10
Hi. I've received your bug and will wait until 2020-02-01 00:00 -0800 PST and then assign the bug to ericng@google.com.
Description
Version used: Fragment 1.1.0-alpha01, Nav 1.0.0-alpha07
Devices/Android versions reproduced on: All
When using FragmentFactory attached to a fragment manager, FragmentNavigator$Destination.createFragment() throws an "InstantiationException: <Fragment> has no zero argument constructor". It appears that upon creating the nav graph, NavHotsFragment instantiates fragments itself instead of delegating to the fragment manager.