IssueTracker

Component used: Navigation Version used: Snapshot #7634339 or 2.4.0-alpha07 Devices/Android versions reproduced on: Pixel 4a

This issue is related to another fixed issue: https://issuetracker.google.com/issues/194925622

2.4.0-alpha05 introduced a bug where tab reselection causes empty screens, unless the current screen is the startDestination of the root graph.

The issue was fixed in Snapshot #7634339, but it introduced another bug:

Flows collected in compose screens via rememberFlowWithLifecycle(flow).collectAsState(initial) complete early on tab reselection, like in the original issue. About rememberFlowWithLifecycle

Attaching the minimal sample that shows the problem and a video.

In sample view model, there is a simple flow that emits text in some interval.

In 2.4.0-alpha04 - Collecting flows directly via collectAsState or via rememberFlowWithLifecycle works as expected (interval Flow doesn't complete until the user leaves the screen)

In 2.4.0-alpha05-06 - Screen becomes empty on tab reselection

In Snapshot #7634339 / 2.4.0-alpha07:

• Tab reselection doesn't cause empty screens
• Tab reselection doesn't cause early flow completion when collecting interval flow directly via collectAsState
• Tab reselection does cause early flow completion when collecting interval flow wrapped in rememberFlowWithLifecycle