Fixed
Status Update
No update yet.
Comments
zw...@google.com
zw...@google.com
Oh and one more thing I forgot. Fragment A's child fragment is also part of the nested navigation controller, for which the Fragment A contains the root NavHostFragment, and not the root nav controller Fragment A is part of. So maybe it's not due to FragmentManager, maybe it's the nested navigation controller prematurely removing it's own fragment, when exitAnimation starts for it's root/parent fragment A.
Other than that, instanceState of the child fragment is preserved properly when navigating back and forth.. It's just that it's view is removed prematurely for some reason.
Other than that, instanceState of the child fragment is preserved properly when navigating back and forth.. It's just that it's view is removed prematurely for some reason.
Description
To reproduce, change the doc's example (
var taxiData = [
{location: new google.maps.LatLng(37.782551, -122.445368), weight: 1000}
];
Here's a gist to reproduce the issue: