fix: Stop post-unlock nav clobbering the autofill new-entry redirect (v2.14.9) - LockScreen's unlock LaunchedEffect was keyed on both (state.unlocked, autofillPending). The NavHost's autofill effect consumes newEntryRequest synchronously, which flipped autofillPending from true to false mid-unlock and re-fired the LockScreen effect — routing the user to the vault list with popUpTo(0) and overwriting the new-entry editor navigation. - Key the effect on state.unlocked only so autofillPending is captured once at the unlock transition; the NavHost's consume no longer retriggers LockScreen. - 3 AutofillNavRepositoryTest cases (request surfaces payload, blank optional fields are dropped, consume clears so the post-unlock branch cannot re-fire). - VERSION 2.14.8 -> 2.14.9. - gates: testDebugUnitTest 980/0, lintDebug clean, assembleRelease both ABIs.
$ koh steal kepr.uk/peach-android@098f165bba88
·
parent: ba1cd3cf8da3
discussion
log in to leave a comment.