Fixed
Status Update
No update yet.
Comments
su...@google.com
ap...@google.com
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?
su...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ne...@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.
Description
Version used: Android 9 Pie
Add a test facility to reduce minimal work interval from 15 mins to 1 min or less.
Rationale: We must test our app end to end to make sure scheduled periodic jobs to upload business-critical data to back-end are executed correctly. The current minimal periodic work schedule interval is 15 mins, which means rounds of regressions usually take 30-60 mins for just a couple of scenarios. Testing will significantly improve if testers could tune this minimal 15 mins interval to something shorter than 2 mins.
Examples of possible acceptable options to solve this:
- a new option under the Android developer-options menu (just like animations speed)
- a setting in WorkManager's lib to create builds with customized interval