Status Update
No update yet.
Comments
ap...@google.com
From the other issue:
note that it is never the right approach to attach a
<deeplink>to an<activity>destination as that will never give you the right behavior when using anon another app's task (where the system back should immediately take the user back to the app that triggered your deep link). Instead, you should attach your deep link directly to your second activity (either by manually writing the appropriate implicit deep link <intent-filter>or by adding the<deeplink>to the start destination of a nav host in that second activity).
A lint error saying as such when a <deepLink> element is added in Navigation XML would go a really long way to avoiding this case. Our navigation-runtime-lint artifact that would contain this check.
Description
android.arch.work:work-runtime
android.arch.work:work-firebase
Version used:
Devices/Android versions reproduced on:
Reproducible on API 21 emulator with google play services
If OneTimeWorkRequest setInitialDelay() method is set to WorkRequest.MIN_BACKOFF_MILLIS app will crash at runtime with
com.firebase.jobdispatcher.ValidationEnforcer$ValidationException: JobParameters is invalid: Initial backoff must be at least 30s
Therefore, I think WorkRequest.MIN_BACKOFF_MILLIS should be at least 30 seconds, or, perhaps, you could create a separate constant for the initial delay and crash WorkManager always if initial delay is less than 30 seconds, no matter what API level.