Fixed
Status Update
Comments
il...@google.com <il...@google.com>
il...@google.com <il...@google.com> #2
A couple of questions:
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
il...@google.com <il...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
il...@google.com <il...@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
Version used: 1.0.0-alpha09
Would be nice to have an easier way to access the Args class since the getArguments() of a Fragment or getIntent().getExtras() of an Activity aren't available at construction time, meaning you need to use a lazy property delgate.
Wrapping that up in a type safe way that works with the generated Args classes would be greatly preferable.