[david-allison]

Note

Assisted-by: GPT-6-Astra xhigh

Purpose / Description

Fixes main category of failures for #22065

Fixes

• Part of Regression test: fix all fragment lifecycle bugs #22065

Approach

launchCollectionInViewLifecycleScope + onViewCreated

How Has This Been Tested?

This fixes a failing test

Checklist

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner

[mikehardy]

Assisted-by: grok-4.7-medium

Thanks — tying the ManageSpace size collectors to the view lifecycle is the right fix for the startup stress REMOVE case.

Local prep: clean rebase (no push; act SHA f80bc73f). Lint (lintAll, ktlintCheck, lint-rules:test), jacocoUnitTestReport, and release emulator tests on API35_GAPI / emulator-5556 passed (authoritative emulator retry; eight XML harness failures waived as ignore-if-present).

ManageSpaceFragment moves the four StateFlow collectors from initSubscreen() into onViewCreated, using launchCollectionInViewLifecycleScope so work stops when the view is destroyed. FragmentLifecycleFixture drops the ManageSpace knownFailures skip so removed before startup coroutines execute exercises that screen again. observeProgress still collects on the activity scope.

GitHub JUnit (macOS/windows) was still pending at review; everything else required was green.

some acceptable findings, no action required, just leaving for posterity: second commit message “all failures fixed” is broader than this slice of #22065 (NoteEditor/CardBrowser cases remain).