Status Update
No update yet.
Comments
il...@google.com
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
pa...@nearside.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
il...@google.com
-
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.
ap...@google.com
Hmm, I feel the crash might be something related to separate/secondary process.
I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.
Description
Component used: Navigation Version used: 2.3.3 (latest) Devices/Android versions reproduced on: n/a
setup:
reference?description=R.string.fooR.string.fooin order to create a URIResult:
The workaround is obviously to change the nav arg type to String and call
getString, but it's a weird limitation for sibling-module navigation.