Fixed
Status Update
No update yet.
Comments
ap...@google.com
Fundamentally the issue here is that the selection logic happening in composition depends on the text layout result which is available on measure. So we end up using stale TextLayoutResult which causes the issue.
il...@google.com
This is the same exception as in
jb...@google.com
There is a similar problem regarding Magnifier but I don't think these are directly related. The main cause for this issue is the async relation between TextFieldValue and layoutResult. Magnifier related crashes don't seem to be caused by changes in TextFieldValue or layout.
Description
Version used: 28.0.0
Given a back stack of:
A -> B (primary)
When doing a 'singleTop' style operation consisting of popping Fragment B then calling replace(), the primary navigation Fragment is correct:
A -> B2 (primary)
However, if you then proceed to call popBackStack(), the primary navigation Fragment is null, not A:
A, primary = null