IssueTracker

WorkManager Alpha 11

I recently switched my JobManager TriggerContentUri implementation to WorkManager and am noticing a major slowdown in the speed at which it responds to ContentUri changes vs. JobManager.

In JobManager, there is an api call to builder.setTriggerContentMaxDelay() that I use as follows to ensure a response within 3 seconds of the content change - this allows my widget UI to be responsive and show a new calendar event created in the Google Calendar app quickly.

    public static void scheduleJob(Context context) {
        JobScheduler js = context.getSystemService(JobScheduler.class);
        JobInfo.Builder builder = new JobInfo.Builder(JOB_TAG_CALENDAR,
                new ComponentName(context, CalendarContentTriggerJob.class));
        builder.addTriggerContentUri(new JobInfo.TriggerContentUri(CalendarContract.CONTENT_URI,
                JobInfo.TriggerContentUri.FLAG_NOTIFY_FOR_DESCENDANTS));
        builder.setTriggerContentUpdateDelay(DateUtils.SECOND_IN_MILLIS);
        builder.setTriggerContentMaxDelay(3 * DateUtils.SECOND_IN_MILLIS);
        js.schedule(builder.build());
    }

My WorkManager implementation looks as follows. There is no way of specifying a Max Delay and as a result the response to the content change is significantly slower than the JobManager implementation.

    fun scheduleJob() {

            // Define the constraints
            val constraints = Constraints.Builder()
                    .addContentUriTrigger(CalendarContract.CONTENT_URI,  true)
                    .build()

            // Create the job definition
            val calendarSync = OneTimeWorkRequest.Builder(CalendarContentTriggerWorker::class.java)
                    .setConstraints(constraints)
                    .addTag(JOB_TAG_CALENDAR)
                    .build()

            // Start the job
            WorkManager.getInstance().enqueueUniqueWork(JOB_TAG_CALENDAR, ExistingWorkPolicy.REPLACE,
                calendarSync)
        }