Fixed
Status Update
No update yet.
Comments
il...@google.com
ugh thats bad, thanks for filing.
il...@google.com
ap...@google.com
i have the fix ready, waiting for code reviews.
il...@google.com
which version of 3.4 contains this fox?
Im still seeing it with 3.4-rc2
Im still seeing it with 3.4-rc2
ru...@gmail.com
ugh looks like it missed 3.4 and only went into 3.5 :/.
i'll try to cherry-pick it into 3.4 but probably too late to catch 3.4 release.
i'll try to cherry-pick it into 3.4 but probably too late to catch 3.4 release.
[Deleted User] <[Deleted User]>
i cherry picked it but it missed 3.4 :/. it will be in 3.4.1 (if happens). otherwise, it is already in 3.5
il...@google.com
il...@google.com
il...@google.com
ดี
ap...@google.com
akses kartu SD
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.