Fixed
Status Update
Comments
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
jb...@google.com <jb...@google.com> #4
-
Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
-
Dynamic features are not used in the application.
As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.
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=param
the param value turns intonull
on the receiving end. I guess some internal parsing is messed up.I'm attaching a sample project showing this issue.