IssueTracker

Description: When using multiple AndroidFragment instances on a screen, navigating to another screen and then returning can cause the fragments to be incorrectly mapped to previous content. This issue occurs because the fragments are obtained through the call:

fragmentManager.findFragmentById(containerFactory.container.id)

Steps to Reproduce:  
Create a screen with two or possible more AndroidFragment instances.
Navigate to another screen.
Make a change that should result in three AndroidFragment instances in a different order (in previous screen).
Return to the previous screen.

Expected Behavior: The screen should display three AndroidFragment instances in the new order.
Actual Behavior: The first two AndroidFragment instances are incorrectly mapped to the previous content.  
 
Fragment version: 1.8.6
Android Version: API 34
Device Model: Pixel 3a (emulator)