Fixed
Status Update
Comments
su...@google.com <su...@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?
ro...@gmail.com <ro...@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.
Description
Version used:1.0.0-alpha02
Devices/Android versions reproduced on: all
Hi,
maybe I'm missing something in the documentation.
My intention was to create a periodic work that should run once a day (each 24 hours). I did two mistakes: I forgot to give the job a tag, and I forgot to check if the job was already in the queue before enqueueing it.
As result of error n2, each time that a user opens the app, a new job is enqueued. Only one job should be fired a day per user, but in my backend logs I can see that this happens multiple times per user.
As result of the error n1, I can not cancel those jobs (because they do not have a tag). I suppose the only solution is to uninstall the app and install it again.
Maybe it would be a nice feature to have a method to cancel all scheduled works, with or without tags. Or a method to get all current works, without tags, an then cancel them by Id.
Or at least to make the tag for a job mandatory, to be able to cancel the task in the future.
Another question that I did not find answer for is: what happens to current scheduled works, if the tag name is changed? Are the new one enqueued, and the old ones remains alive or what?
Thank and apologizes about my English.