IssueTracker

When using the new fragment state manager, if a fragment is inflated after the host activity is RESUMED, via either the deprecated <fragment> tag or FragmentContainerView, the fragment never makes it to a RESUMED state.

In the case of the <fragment> tag:

• the fragment is moved to VIEW_CREATED and never makes it any further

for FragmentContainerView:

• the fragment correctly moves to RESUMED the first time, but on configuration change, the view that inflates the fragment is never attached to the new view hierarchy, so the fragment is RESUMED but never actually visible.

We should address this issue for both components. aosp/1591056 and aosp/1593053 have been implemented for the <fragment> tag case. This bug will track the FragmentContainerView case.