Fixed
Status Update
Comments
se...@google.com <se...@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?
ap...@google.com <ap...@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
Component used: lifecycle-livedata-kt
Version used: 2.3.0-alpha02
Devices/Android versions reproduced on: N/A
According to the release note , a new lint check for the null value of MutableLiveData is released.
However, It seems not available yet.
In addition, I tried the lint check from AOSP source code, but it fails.
The lint check with a local variable is working. But, instance fields like below code is failed.
Part of the stack trace. I will attach the full stack trace file.
(Run
LINT_PRINT_STACKTRACE=true ./gradlew lint
)Thanks