Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
yea i'll take it.
jb...@google.com
Thanks for the detailed analysis. This may not be an issue anymore since we've started using Main.immediate there but I' not sure; I'll try to create a test case.
Description
Component used: Navigation
Version used: 2.4.0-beta02
Devices/Android versions reproduced on: Pixel 3 API 31 emulator, Pixel 3 physical device with Android 12
When you pass an optional value that is equal to its key name the value gets lost and the NavBackStackEntry reveives
null(or default value if it's set). If any other value is passed everything is correct.For example when I navigate to route
secondary?param=paramthe param value turns intonullon the receiving end. I guess some internal parsing is messed up.I'm attaching a sample project showing this issue.