IssueTracker

Component used: Fragment
Version used: 1.2.0-rc03

In the rare case where a retained fragment is added after the state is saved (specifically, in the case covered by the restoreRetainedInstanceFragmentWithTransparentActivityConfigChange test), we need to ensure that the retained fragment is both destroyed (which we do already) *and* removed from the list of retained fragments.

If the fragment is not removed from the list of retained fragments, it is recreated after each config change, only to be immediately destroyed again.