IssueTracker

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.

Ok I just tested it, and it is due to nested navigation graph. When I include a child fragment directly into Fragment A, without navigation, it's not removed prematurely and it's working as intended.

So where do we go from here, is this a bug for you to fix, or there's something wrong with my nested navigation graph implementation, in which case I'd like you to point me in the right direction how to fix it?

Here you go: https://drive.google.com/file/d/12Tz8YjCEbcs4LzxqL4352zUJyPvJ_GLt/view?usp=sharing

I slowed down the animations so you can see what's happening.

Root Fragment A is the one with BottomNavigationBar on the bottom.
GREEN - Fragment A's CHILD fragment (the one that's disappearing)
RED - Destination Fragment

Press "Settings" in the action menu on the upper right to start navigation. Observe how Root Fragment A is visible during the whole animation with it's BottomNavigationBar, but it's CHILD GREEN fragment disappears immediately, as it is part of the nested navigation graph hosted in the Fragment A itself.

On the way back, Fragment A is properly recreated with it's green child fragment, and both are visible properly (when going back in the direction A <- B).

I'm having trouble downloading your project from Google Drive for some reason. Would you mind attaching it here directly?

I suspect this is a Fragment issue and not something Navigation can control. I'd be interested to know if you run into the same issue if you have *any* Fragment, rather than a NavHostFragment, between your child of A and A itself.

I'll test that too when I have some time, though it might not be soon.

I'll attach the project directly so you can test it yourself, and if it is the problem with Fragments, then let's open the issue for Fragments..

Thanks, we've confirmed this is a problem with Fragments and have marked it as a duplicate of the relevant Fragment issue.

Project: platform/frameworks/support
Branch: androidx-master-dev

commit c53170c58309d7370d63d5386e83fce4cee02ba2
Author: jbwoods <jbwoods@google.com>
Date:   Wed Jun 26 17:58:38 2019

    Avoid grandchild Fragment animations running during parent Fragment transactions
   
    Follow-up to aosp/951635. Child fragment views are not destroyed when the parent
    is animated, but grandchild fragment views are.
   
    This change checks up the ancestor hierarchy to ensure fragment views
    will not be destroyed if any of its ancestors are being removed.
   
    Test: Added unit Test
    BUG: 116675313
    Change-Id: Ie65ae2fb150340b51bb0362cfa84f320ee2e8c7e

M       fragment/fragment/src/androidTest/java/androidx/fragment/app/FragmentAnimationTest.kt
M       fragment/fragment/src/main/java/androidx/fragment/app/Fragment.java
M       fragment/fragment/src/main/java/androidx/fragment/app/FragmentManagerImpl.java

https://android-review.googlesource.com/1001542
https://goto.google.com/android-sha1/c53170c58309d7370d63d5386e83fce4cee02ba2

This has been fixed internally and will be available in the Fragment  1.2.0-alpha01 release.