Status Update
No update yet.
Comments
ya...@google.com
da...@google.com
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
ap...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
da...@google.com
ys...@gmail.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.
nn...@gmail.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
@Entity
data class User(
@PrimaryKey id: Long,
name: String,
email: String?
)
data class UserName(id: Long, name: String)
data class UserEmail(id: Long, email: String)
@Dao
interface UserDao {
@Insert(entity = User::class)
insertWithoutEmail(userName: UserName)
@Update(entities = User::class)
updateEmail(userEmail: UserEmail)
}
- The @Insert example above is a bit silly, but it makes sense when you want to leave out columns with default values (
- We probably need a better API to support insertion/update of multiple entities/pojos.