Objective
Update Navigation3 from 1.1.4 directly to stable 1.1.7 as one independently reviewable/revertible dependency patch after the current U0/U1/M0 stabilization baseline is accepted.
AndroidX stable-channel lists Navigation3 1.1.7 as stable on 2026-08-26, superseding the previously planned 1.1.6 target. Owner under #179. #190 remains a combined compatibility probe only and must not be merged as the implementation vehicle.
Why this matters to MuxTV
The 1.1.4 -> 1.1.7 jump accumulates TV-relevant navigation correctness fixes. Official 1.1.7 notes specifically fix predictive-back triggered during an unfinished forward transition so progress animates and completes correctly. 1.1.6 also fixed SaveableStateHolder key reuse failures when multiple pop transitions are in flight due to rapid back-stack popping.
Repeated Back/D-pad interaction before animations settle is realistic on Android TV, so this is correctness hardening rather than version-chasing.
Scope
- version change
1.1.4 -> 1.1.7 only;
- source/API adaptations only if compilation proves strictly required;
- add focused rapid repeated Back/pop and open -> Back-before-transition-complete regression coverage where current tests cannot express the fixed modes;
- preserve
focusRestorer() and destination state ownership unless separate evidence proves a defect;
- no navigation architecture rewrite;
- no U0 geometry/token redesign;
- no unrelated dependency bundle upgrades.
Acceptance
- exact dependency resolution is Navigation3
1.1.7 with no mixed family versions;
- host unit/Compose/navigation tests green on exact head;
- rapid repeated Back/pop behavior covered;
- open -> Back before forward transition completion covered;
- rail/content focus restoration semantics remain unchanged;
- canonical current API navigation/focus regression green;
- API26 compatibility smoke where risk routing requires it;
- no extra AVD identity and no visual redesign.
Ordering
Do not merge before U0/U1 freeze the UI/navigation baseline. Prefer after #178/M0 as well so dependency movement cannot contaminate the measurement baseline.
Official reference
https://developer.android.com/jetpack/androidx/releases/navigation3
Objective
Update Navigation3 from
1.1.4directly to stable1.1.7as one independently reviewable/revertible dependency patch after the current U0/U1/M0 stabilization baseline is accepted.AndroidX stable-channel lists Navigation3
1.1.7as stable on 2026-08-26, superseding the previously planned1.1.6target. Owner under #179. #190 remains a combined compatibility probe only and must not be merged as the implementation vehicle.Why this matters to MuxTV
The
1.1.4 -> 1.1.7jump accumulates TV-relevant navigation correctness fixes. Official 1.1.7 notes specifically fix predictive-back triggered during an unfinished forward transition so progress animates and completes correctly. 1.1.6 also fixedSaveableStateHolderkey reuse failures when multiple pop transitions are in flight due to rapid back-stack popping.Repeated Back/D-pad interaction before animations settle is realistic on Android TV, so this is correctness hardening rather than version-chasing.
Scope
1.1.4 -> 1.1.7only;focusRestorer()and destination state ownership unless separate evidence proves a defect;Acceptance
1.1.7with no mixed family versions;Ordering
Do not merge before U0/U1 freeze the UI/navigation baseline. Prefer after #178/M0 as well so dependency movement cannot contaminate the measurement baseline.
Official reference
https://developer.android.com/jetpack/androidx/releases/navigation3