title: Nested fragments disappear during transition animation
body: <p>Here's the scenario: Activity contains fragment <code>A</code>, which in turn uses <code>getChildFragmentManager()</code> to add fragments <code>A1</code> and <code>A2</code> in its <code>onCreate</code> like so:</p>
  
  <pre><code>getChildFragmentManager()
    .beginTransaction()
    .replace(R.id.fragmentOneHolder, new FragmentA1())
    .replace(R.id.fragmentTwoHolder, new FragmentA2())
    .commit()
  </code></pre>
  
  <p>So far, so good, everything is running as expected.</p>
  
  <p>We then run the following transaction in the Activity: </p>
  
  <pre><code>getSupportFragmentManager()
    .beginTransaction()
    .setCustomAnimations(anim1, anim2, anim1, anim2)
    .replace(R.id.fragmentHolder, new FragmentB())
    .addToBackStack(null)
    .commit()
  </code></pre>
  
  <p>During the transition, the <code>enter</code> animations for fragment <code>B</code> runs correctly but <strong>fragments A1 and A2 disappear entirely</strong>. When we revert the transaction with the Back button, they initialize properly and display normally during the <code>popEnter</code> animation.</p>
  
  <p>In my brief testing, it got weirder - if I set the animations for the child fragments (see below), the <code>exit</code> animation runs intermittently when we add fragment <code>B</code></p>
  
  <pre><code>getChildFragmentManager()
    .beginTransaction()
    .setCustomAnimations(enter, exit)
    .replace(R.id.fragmentOneHolder, new FragmentA1())
    .replace(R.id.fragmentTwoHolder, new FragmentA2())
    .commit()
  </code></pre>
  
  <p>The effect I want to achieve is simple - I want the <code>exit</code> (or should it be <code>popExit</code>?) animation on fragment <code>A</code> (anim2) to run, animating the whole container, including its nested children. </p>
  
  <p>Is there any way to achieve that?</p>
  
  <p><strong>Edit</strong>: Please find a test case <a href="https://github.com/BurntBrunch/NestedFragmentsAnimationsTest">here</a></p>
  
  <p><strong>Edit2</strong>: Thanks to @StevenByle for pushing me to keep trying with the static animations. Apparently you can set animations on a per-op basis (not global to the whole transaction), which means the children can have an indefinite static animation set, while their parent can have a different animation and the whole thing can be committed in one transaction. See the discussion below and the <a href="https://github.com/BurntBrunch/NestedFragmentsAnimationsTest">updated test case project</a>.</p>