Periodic work is not triggered more than once on 1.0.0-alpha07 [112859683]

Fixed

Bug

Status Update

No update yet.

Description

ne...@gmail.com

created issue #1

Aug 20, 2018 10:08PM

Component used: WorkManager
Version used: 1.0.0-alpha07
Devices/Android versions reproduced on: Pixel 2, Android 9 Pie

The work request below is executed once but not periodically on version alpha07, this works correctly and periodically on version alpha06

val constraints = androidx.work.Constraints.Builder()
.setRequiredNetworkType(NetworkType.CONNECTED)
.build() // Run only when network is available
val workRequest =
PeriodicWorkRequestBuilder<ReportUploader>(REPORTING_REPEAT_INTERVAL_IN_MINUTES, TimeUnit.MINUTES)
.addTag(REPORTER_TAG)
.setConstraints(constraints)
.setBackoffCriteria(BackoffPolicy.EXPONENTIAL, 10, TimeUnit.SECONDS)
.build() // Run every 15 mins
workManager
.enqueueUniquePeriodicWork(REPORTER_TAG, ExistingPeriodicWorkPolicy.KEEP, workRequest)

Comments

ne...@gmail.com <ne...@gmail.com> #2Aug 20, 2018 10:10PM

Project: platform/frameworks/support
Branch: androidx-master-dev

commit 87f4c988b713e43deef88a0df6a31c507f11b4a8
Author: Jeremy Woods <jbwoods@google.com>
Date: Wed May 27 11:20:32 2020

Use setMaxLifecycle for FragmentScenario moveToState

Current FragmentScenario uses ActivityScenario to for the moveToState
method. That means moving to STARTED does not work prior to API 23. This
also means that tests including DialogFragment cannot be moved to
CREATED, only ACTIVITY_CREATED.

This change uses setMaxLifecycle instead, so that FragmentScenario is
decoupled from ActivityScenario and there are no longer any restrictions
on moving to API 23 and DialogFragment's can be properly moved to
CREATED.

Test: ran tests on API 21 device and they passed
Bug: 156527405
Change-Id: I63d5facfcce9875acf06e39029686cb535cc3ea6

M fragment/fragment-testing/src/androidTest/java/androidx/fragment/app/testing/FragmentScenarioDialogFragmentTest.kt
M fragment/fragment-testing/src/androidTest/java/androidx/fragment/app/testing/FragmentScenarioTest.kt
M fragment/fragment-testing/src/main/java/androidx/fragment/app/testing/FragmentScenario.java

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

ra...@google.com <ra...@google.com> Aug 21, 2018 11:33PM

Assigned to ra...@google.com.

su...@google.com <su...@google.com> Aug 21, 2018 11:45PM

Accepted by su...@google.com.

ap...@google.com <ap...@google.com> #3Aug 22, 2018 12:44AM

This has been fixed internally and will be available in Fragment 1.3.0-alpha07.

lo...@gmail.com <lo...@gmail.com> #4Aug 22, 2018 03:24PM

I am experiencing the same problem using the following code:

val myWorker = PeriodicWorkRequestBuilder<MyWorker>(15, TimeUnit.MINUTES)

myWorker.addTag(NEWSFEED_SYNC_WORKER_ID)

val constraints = Constraints.Builder()
.setRequiredNetworkType(NetworkType.CONNECTED)
.build()
myWorker.setConstraints(constraints)

WorkManager.getInstance().enqueue(myWorker.build())

su...@google.com <su...@google.com> #5Aug 22, 2018 04:03PM

Marked as fixed.

The fix will be available in alpha08.

ta...@gmail.com <ta...@gmail.com> #6Oct 6, 2018 09:23AM

I'm facing this in alpha09 on Android Pie

ta...@gmail.com <ta...@gmail.com> #7Oct 7, 2018 09:48AM

Update: alpha09 works fine in pre-Oreo with a minimum interval of 15 minutes. Post Oreo, never gets triggered. Haven't yet checked the interference of battery optimization. Will update on the same soon.

ah...@gmail.com <ah...@gmail.com> #8Nov 4, 2018 09:36AM

Still facing this in alpha10 on Oreo and Pie

ar...@gmail.com <ar...@gmail.com> #9Nov 22, 2018 06:10PM

solved in alpha 11 i have not this problem but some times WorkManger run 2 times instead one Worker class in Periodic work

pr...@gmail.com <pr...@gmail.com> #10Nov 24, 2018 09:32AM

Is there any other way to use periodic job scheduler except WorkManager,Job Creator?