ContentResolver.SyncExtrasScheduleAsExpeditedJob Field
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Run this sync operation as an "expedited job"
(see android.app.job.JobInfo.Builder#setExpedited(boolean)
).
[Android.Runtime.Register("SYNC_EXTRAS_SCHEDULE_AS_EXPEDITED_JOB", ApiSince=31)]
public const string SyncExtrasScheduleAsExpeditedJob;
[<Android.Runtime.Register("SYNC_EXTRAS_SCHEDULE_AS_EXPEDITED_JOB", ApiSince=31)>]
val mutable SyncExtrasScheduleAsExpeditedJob : string
Field Value
- Attributes
Remarks
Run this sync operation as an "expedited job" (see android.app.job.JobInfo.Builder#setExpedited(boolean)
). Normally (if this flag isn't specified), sync operations are executed as regular android.app.job.JobService
jobs.
Because Expedited Jobs have various restrictions compared to regular jobs, this flag cannot be combined with certain other flags, otherwise an IllegalArgumentException
will be thrown. Notably, because Expedited Jobs do not support various constraints, the following restriction apply: <ul> <li>Can't be used with #SYNC_EXTRAS_REQUIRE_CHARGING
<li>Can't be used with #SYNC_EXTRAS_EXPEDITED
<li>Can't be used on periodic syncs. <li>When an expedited-job-sync fails and a retry is scheduled, the retried sync will be scheduled as a regular job unless #SYNC_EXTRAS_IGNORE_BACKOFF
is set. </ul>
This is different from #SYNC_EXTRAS_EXPEDITED
.
Java documentation for android.content.ContentResolver.SYNC_EXTRAS_SCHEDULE_AS_EXPEDITED_JOB
.
Portions of this page are modifications based on work created and shared by the Android Open Source Project and used according to terms described in the Creative Commons 2.5 Attribution License.