IssueTracker

Thanks for the report - do you have any reproduction steps?

Nevermind, this has been fixed and will be available in an upcoming release.

An unfortunate side effect of this seems to be that the adapter is set to null before any pending fragment animations are completed.

In my project I add a PreferenceFragmentCompat to the backstack, specifying custom enter and exit animations. Now, when the user presses the back button I call FragmentManager.popBackStack() which in turn starts the custom exit animation.

The problem is that popBackstack() internally calls onDestroyView() on the PreferenceFragmentCompat to be removed. The PreferenceFragmentCompat calls unbindPreferences() which calls getListView().setAdapter(null).

The effect is that the list of preference items is cleared instantly before the exit animation even starts! This causes a white flicker and is clearly noticeable, the preference items disappear, then the view fades out.

Could you prevent setAdapter(null) from being called in this scenario? Maybe unregister the data observer instead?

I can confirm that using fragment 1.2.2 resolves the issue, thank you!

Without an explicit dependency declaration version 1.1.0 was still used (transient dependency of appcompat 1.1.0).

Use logcat, or use the various getStatus methods to see what's going on.  File a bug with a bugreport and sample code that results in the problem.

It would be nice to see setInitialDelay() on PeriodicWorkRequest.Builder in the next version, Thanks

Just a "+1" "me too" to add another voice to this... would make so much sense to be able to have setInitialDelay() on PeriodicWorkRequest.Builder

Android must list down the challenges of Periodic Work request  in there documents, I am  tracking Work Manager since it was alpha.Here are the limitations of Priodic Work request:
1. Periodic work request does not support setInitialDelay.
2. Periodic Work request does not support the Chining.

Both of these items are listed in the official documentation for PeriodicWorkRequest: https://developer.android.com/reference/androidx/work/PeriodicWorkRequest

"Periodic work has a minimum interval of 15 minutes and it cannot have an initial delay."
"Periodic work cannot be part of a chain or graph of work."

Still not supported...
I feel that many people need it...would make so much sense to be able to have setInitialDelay() on PeriodicWorkRequest.Builder

Setting a flex period effectively delays a PeriodicWorkRequest.

+1 from me too, with an extra option to limit the number of repeats, for example, run a periodic job daily for 7 days and then stop.

+1 for setInitailDelay() and limitNumberOfFires() for Periodic work request!

What is the best solution for now to setInitailDelay() ?

You can use a PeriodicWorkRequest.Builder with a flex Period as suggested in #13.
This behaviour is documented: https://developer.android.com/reference/androidx/work/PeriodicWorkRequest.Builder#PeriodicWorkRequest.Builder(java.lang.Class%3C?%20extends%20androidx.work.ListenableWorker%3E,%20long,%20java.util.concurrent.TimeUnit,%20long,%20java.util.concurrent.TimeUnit)

The call creates a PeriodicWorkRequest to run periodically once within the flex period of every interval period.

What I mean by setInitailDelay() is the delay before the first run then a fixed periodic delay.

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

commit 25dc21990f5b0d606f3141b9120516b880599b6c
Author: Rahul Ravikumar <rahulrav@google.com>
Date:   Mon Apr 29 10:27:18 2019

    Add support for initialDelays for PeriodicWorkRequests.
   
    Test: Additional WorkSpecTest unit tests.
    Integration tests on API 23, and API 21.
   
    Fixes: b/111404867
   
    Change-Id: I9eae1c7cf527c231b831f22c6a2d10089d6a63c9

M       work/integration-tests/testapp/src/main/java/androidx/work/integration/testapp/MainActivity.java
M       work/integration-tests/testapp/src/main/res/layout/activity_main.xml
M       work/integration-tests/testapp/src/main/res/values/strings.xml
M       work/workmanager/api/2.1.0-alpha01.txt
M       work/workmanager/api/current.txt
M       work/workmanager/src/androidTest/java/androidx/work/WorkSpecTest.java
M       work/workmanager/src/main/java/androidx/work/OneTimeWorkRequest.java
M       work/workmanager/src/main/java/androidx/work/WorkRequest.java
M       work/workmanager/src/main/java/androidx/work/impl/WorkerWrapper.java
M       work/workmanager/src/main/java/androidx/work/impl/background/systemjob/SystemJobScheduler.java
M       work/workmanager/src/main/java/androidx/work/impl/model/WorkSpec.java

https://android-review.googlesource.com/953484
https://goto.google.com/android-sha1/25dc21990f5b0d606f3141b9120516b880599b6c

still can't rely on it :(
I calculate millis to midnight and schedule a daily backup with PeriodicWorkRequest (should happen each 24h), and it just won't fire up the Worker.
When I remove setInitialDelay() call, PeriodicWorkRequest - it works!

classic