Fixed
Status Update
Comments
da...@google.com <da...@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?
se...@gmail.com <se...@gmail.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
da...@google.com <da...@google.com>
ap...@google.com <ap...@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: Room
Version used: 2.3.0-alpha04
Devices/Android versions reproduced on: Emulator API 26 with google services
Case 1: Consider Base DAO class
And class
It is expected that the generated implementation code will have 3 Update methods with corresponding conflict strategies.
What is actually generated:
Actual - all update methods are using the same adapter with ABORT.
Case 2: Change very first update strategy to IGNORE in BaseDao
And now adapter becomes:
Case 3: Use case 2 and add a new method to ComanyDao:
then update implementation becomes