WorkManager Periodic work stops after a period [111469837]

Fixed

Bug

Status Update

No update yet.

Description

da...@gmail.com

created issue #1

Jul 15, 2018 06:15PM

I'm using WorkManager alpha-4 and have converted my app's sync jobs to workers. If the device remains plugged in, the periodic jobs run as expected (approx once an hour as scheduled). However, when taking the device off power, allowing it to go to sleep, after a period of time the workers no longer excecute.

My log contains the following statements at the time when the jobs (there are 4) were supposed to execute:

2018-07-15 13:52:15.456 12947-12947/com.dvtonder.chronus D/SystemJobService: Override deadline expired for id 5caee77a-e9c5-4a99-bc7b-651ad21eb94b. Retry requested
2018-07-15 13:52:15.460 12947-12947/com.dvtonder.chronus D/SystemJobService: Override deadline expired for id e3641a8b-1df8-49b9-8c90-1c893c3afc0f. Retry requested
2018-07-15 13:52:15.464 12947-12947/com.dvtonder.chronus D/SystemJobService: Override deadline expired for id db7c03a2-0fe6-42c4-baf8-0ef6e8220e9b. Retry requested
2018-07-15 13:52:15.465 12947-12947/com.dvtonder.chronus D/SystemJobService: Override deadline expired for id d3efce3a-6aa7-4e10-84af-759f1124ccf5. Retry requested

As you can see from the log entries below, things were running just fine up to that point:

2018-07-15 11:30:02.168 12947-12947/com.dvtonder.chronus D/SystemJobService: 5caee77a-e9c5-4a99-bc7b-651ad21eb94b executed on JobScheduler
2018-07-15 11:30:02.396 12947-12947/com.dvtonder.chronus D/SystemJobService: d3efce3a-6aa7-4e10-84af-759f1124ccf5 executed on JobScheduler
2018-07-15 11:30:03.291 12947-12947/com.dvtonder.chronus D/SystemJobService: e3641a8b-1df8-49b9-8c90-1c893c3afc0f executed on JobScheduler
2018-07-15 11:30:03.292 12947-12947/com.dvtonder.chronus D/SystemJobService: db7c03a2-0fe6-42c4-baf8-0ef6e8220e9b executed on JobScheduler
2018-07-15 11:54:09.377 12947-12947/com.dvtonder.chronus D/SystemJobService: onStartJob for b4303ff7-dd6c-4288-8be2-e859c56cddc5
2018-07-15 11:54:09.383 12947-12947/com.dvtonder.chronus D/SystemJobService: onStartJob for 27c2a27b-4da0-4512-ac60-924fb134addd
2018-07-15 11:54:09.478 12947-12947/com.dvtonder.chronus D/SystemJobService: 27c2a27b-4da0-4512-ac60-924fb134addd executed on JobScheduler
2018-07-15 11:54:10.026 12947-12947/com.dvtonder.chronus D/SystemJobService: b4303ff7-dd6c-4288-8be2-e859c56cddc5 executed on JobScheduler
2018-07-15 12:49:00.838 12947-12947/com.dvtonder.chronus D/SystemJobService: onStartJob for e3641a8b-1df8-49b9-8c90-1c893c3afc0f
2018-07-15 12:49:00.865 12947-12947/com.dvtonder.chronus D/SystemJobService: onStartJob for 5caee77a-e9c5-4a99-bc7b-651ad21eb94b
2018-07-15 12:49:01.136 12947-12947/com.dvtonder.chronus D/SystemJobService: onStartJob for db7c03a2-0fe6-42c4-baf8-0ef6e8220e9b
2018-07-15 12:49:01.548 12947-12947/com.dvtonder.chronus D/SystemJobService: onStartJob for d3efce3a-6aa7-4e10-84af-759f1124ccf5
2018-07-15 12:49:09.589 12947-12947/com.dvtonder.chronus D/SystemJobService: db7c03a2-0fe6-42c4-baf8-0ef6e8220e9b executed on JobScheduler
2018-07-15 12:49:17.334 12947-12947/com.dvtonder.chronus D/SystemJobService: d3efce3a-6aa7-4e10-84af-759f1124ccf5 executed on JobScheduler
2018-07-15 12:49:25.292 12947-12947/com.dvtonder.chronus D/SystemJobService: e3641a8b-1df8-49b9-8c90-1c893c3afc0f executed on JobScheduler
2018-07-15 12:49:42.364 12947-12947/com.dvtonder.chronus D/SystemJobService: 5caee77a-e9c5-4a99-bc7b-651ad21eb94b executed on JobScheduler
2018-07-15 12:50:03.938 12947-12947/com.dvtonder.chronus D/SystemJobService: onStartJob for 7fa7b9d0-4e00-466f-a29d-fcc89d4c5b5d
2018-07-15 12:50:04.015 12947-12947/com.dvtonder.chronus D/SystemJobService: 7fa7b9d0-4e00-466f-a29d-fcc89d4c5b5d executed on JobScheduler
2018-07-15 12:50:32.909 12947-12947/com.dvtonder.chronus D/SystemJobService: onStartJob for 204b2e5e-5e24-466e-bdd7-814ef9a4582b
2018-07-15 12:50:33.329 12947-12947/com.dvtonder.chronus D/SystemJobService: 204b2e5e-5e24-466e-bdd7-814ef9a4582b executed on JobScheduler
2018-07-15 13:52:15.456 12947-12947/com.dvtonder.chronus D/SystemJobService: Override deadline expired for id 5caee77a-e9c5-4a99-bc7b-651ad21eb94b. Retry requested
2018-07-15 13:52:15.460 12947-12947/com.dvtonder.chronus D/SystemJobService: Override deadline expired for id e3641a8b-1df8-49b9-8c90-1c893c3afc0f. Retry requested
2018-07-15 13:52:15.464 12947-12947/com.dvtonder.chronus D/SystemJobService: Override deadline expired for id db7c03a2-0fe6-42c4-baf8-0ef6e8220e9b. Retry requested
2018-07-15 13:52:15.465 12947-12947/com.dvtonder.chronus D/SystemJobService: Override deadline expired for id d3efce3a-6aa7-4e10-84af-759f1124ccf5. Retry requested

Comments

ra...@google.com <ra...@google.com> #2Jul 16, 2018 04:50PM

Status: Won't Fix (Intended Behavior)

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android build

Which Android build are you using? (e.g. OPP1.170223.012)

Device used - Device Make, Model, Android OS Version

Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Android bug report capturing

After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory.

Alternate method

Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Screen record of the issue, for clarity

Please capture screen record or video of the issue using following steps:

adb shell screenrecord /sdcard/video.mp4

Subsequently use following command to pull the recorded file:

adb pull /sdcard/video.mp4

Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.

da...@gmail.com <da...@gmail.com> #3Jul 16, 2018 06:03PM

android 9, 10, 11, 12
Devices: samsung, realme, xiaomi, OPPO, motorola, LGE,

I don't know how to write code reproducing issues in Android framework, unless you explain what does "no event down from INITIALIZED" mean. Then maybe I can prepare a piece of code that doesn't "event down from INITIALIZED". Until then - sorry.

Also - this error doesn't ever show on the device it is just logged to crashlytics, so there's now way to capture anything "after reproducing the issue".

da...@gmail.com <da...@gmail.com> #4Jul 16, 2018 09:15PM

That particular error means that you are attempting to move the Lifecycle to DESTROYED before it was actually ever moved to CREATED. It was never actually supposed to be supported, but there was a bug in Lifecycle that made it so it only failed if there was an Observer on the Lifecycle, but it was fixed in https://issuetracker.google.com/177924329.

ra...@google.com <ra...@google.com> #5Jul 16, 2018 09:25PM

Glad to hear it was fixed. I'm experiencing it with lifecycle 2.5.1.

da...@gmail.com <da...@gmail.com> #6Jul 16, 2018 09:42PM

I mean it was fixed to throw the error in Lifecycle 2.5. It was always supposed to be an error.

da...@gmail.com <da...@gmail.com> #7Jul 16, 2018 11:03PM

So some thing (implementing some lifecycle interface I guess?) somewhere tries to go into destroyed state before this thing was even created.

Whoa! That's some info!

Now - how can I, having this error message and error stack, discover WHAT exactly is causing this error?

Because, you know, I don't really create thingies having their own lifecycle...

ra...@google.com <ra...@google.com> #8Jul 18, 2018 06:27PM

Assigned to ra...@google.com.

Well from the stack, your Activity is being started and the fragment is getting destroyed.

So there is some fragment that is added to your activity that is being removed before it's Lifecycle goes to CREATED.

su...@google.com <su...@google.com> Jul 23, 2018 09:53PM

Marked as fixed.

da...@gmail.com <da...@gmail.com> #9Aug 26, 2018 04:28PM

OK, that might indeed help finding something, if indeed I'm destroying a fragment before it was created (although I have no idea how to do such stunt). But would it be impossible to include component name in the error, like i.e. in this helpful and friendly exception:

java.lang.IllegalStateException: The content of the adapter has changed but ListView did not receive a notification. Make sure the content of your adapter is not modified from a background thread, but only from the UI thread. Make sure your adapter calls notifyDataSetChanged() when its content changes. [in ListView(2131230928, class android.widget.ListView) with Adapter(class com.students.post.Post_Fragment$Post_listAdapter)]

su...@google.com <su...@google.com> #10Aug 27, 2018 07:36PM

The LifecycleOwner is indeed available from the LifecycleRegistry so we can add that as part of the message so you know which component it is referring to.

sa...@gmail.com <sa...@gmail.com> #11Jun 27, 2019 08:20AM

That would be most helpful, thanks! Can you somehow estimate a timeframe for that fix?

ra...@google.com <ra...@google.com> #12Jun 27, 2019 02:21PM

Project: platform/frameworks/support
Branch: androidx-main

commit e7dfcd2e09ee1dd3589fbd548f50617a8f1c1356
Author: sanura <sanura@google.com>
Date: Thu Oct 13 03:07:32 2022

Update LifecycleRegistry.moveToState() error message

Include the name of the component in the error
message for LifecycleRegistry.moveToState() to
better help developers debug which component is
trying to do an illegal state movement.

RelNote: "`LifecycleRegistry.moveToState()` now
includes more helpful error messaging that informs
developers of the component causing the error."
Test: moveInitializedToDestroyed update
Bug: 244910446

Change-Id: Idf4b23476f809e6c6ff2361d9e864653c90fea2a

M lifecycle/lifecycle-runtime/src/main/java/androidx/lifecycle/LifecycleRegistry.java
M lifecycle/lifecycle-runtime/src/test/java/androidx/lifecycle/LifecycleRegistryTest.java

https://android-review.googlesource.com/2253416