Status Update
Comments
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
sa...@google.com <sa...@google.com>
g....@xe.gr <g....@xe.gr> #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.
pr...@google.com <pr...@google.com> #5
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: livecycle-livedata-ktx Version used: 2.5.1
distinctUntilChanged()
which does not set the initial value of the returned LiveData even if the source one was initialized. This caused unnecessary recompositions if observed withobserveAsState()
.However, I also noticed that the other two
Transformations
methods,map
andswitchMap
, suffer from the same symptom which means that they too will likely cause the same unnecessary recompositions.