Status Update
Comments
ra...@google.com <ra...@google.com>
ra...@google.com <ra...@google.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
lb...@gmail.com <lb...@gmail.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
su...@google.com <su...@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.
lb...@gmail.com <lb...@gmail.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
Version used:
implementation "android.arch.work:work-runtime-ktx:1.0.0-alpha04"
implementation "android.arch.work:work-firebase:1.0.0-alpha04"
But also the Java one
Devices/Android versions reproduced on:
Nexus 4 with Android 4.4.4
If this is a bug in the library, we would appreciate if you could attach:
- Sample project to trigger the issue.
Attached
- A screenrecord or screenshots showing the issue (if UI related).
Attached.
The bug is that on newer Android versions, the schedule works fine, yet here on this Android version, the work never gets called.
In the sample, I've scheduled it to run in 30 seconds:
workManager.enqueue(OneTimeWorkRequest.Builder(SampleJob::class.java).addTag(schedultedTag).setInitialDelay(30, TimeUnit.SECONDS).build())
Steps for reproducing the bug:
1. Just press on "schedule job in 30 sec" button.
2. You can wait 30 seconds or even a lot more time, and it won't be launched. I've set that a toast and log will b shown. Nothing occurs.
If I remove the delay, it works fine :
workManager.enqueue(OneTimeWorkRequest.Builder(SampleJob::class.java).addTag(normalJobTag).build())
Same goes if I remove the Firebase usage:
implementation "android.arch.work:work-firebase:1.0.0-alpha04"