Fixed
Status Update
Comments
ch...@google.com <ch...@google.com>
mt...@gmail.com <mt...@gmail.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.
va...@google.com <va...@google.com>
pr...@google.com <pr...@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
Some of the
***Resource
helpers are not configuration-changing aware.Specifically,
integerResource
integerArrayResource
dimensionResource
booleanResource
colorResource
fontResource
all do not have a key on
Configuration
, unlikestringResource
,painterResource
and others.This means that this resources will not correctly update if the configuration changes (changing the resource value) and the
Activity
is not recreated (due to opting out of recreation).