IssueTracker

Please restart the device and check for this issue on the latest software build. If the issue is still reproducible please share the bugreport(to be captured immediately after resolving the issue) and screenrecord of the issue.

Android bug report (to be captured after reproducing the issue) For steps to capture a bug report, please refer: https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Screen Record of the Issue Please capture screen record or video of the issue using following steps: adb shell screenrecord /sdcard/video.mp4 Subsequently use following command to pull the recorded file: adb pull /sdcard/video.mp4 Attach the file to this issue.

Please restart the device and check if the issue persists?

The issue has been fixed and it will be available in a future build.Please refer the release notes link https://developer.android.com/about/versions/13/release-notes.

Ah yes, that can make sense. IIRC, the WorkManager plays with enabling/disabling components, which resets the app widget component in the system. In turn, the system then replaces the app widget with the initial layout, and then calls your app to get the real view. That would definitely flicker.

Willie, didn't you have a work around involving posting a job with a really long expiry time?

Yes, this is a known issue, see also https://issuetracker.google.com/issues/180436098, and https://issuetracker.google.com/issues/115575872 for more details.

The workaround is to create a one-time Worker set to 10 years out, (use setInitialDelay) and set at least one constraint on it. This ensures that the WorkManager component is not disabled and an app widget update is not triggered inadvertently. You can use ExistingWorkPolicy.KEEP to ensure that subsequent enqueues no-op.

This can look something like:

fun enqueueDelayedWorker(context: Context, workerClass: Class<out ListenableWorker>) {
    WorkManager.getInstance(context).enqueueUniqueWork(
        "appWidgetWorkerKeepEnabled",
         ExistingWorkPolicy.KEEP,
         OneTimeWorkRequest.Builder(workerClass)
            .setInitialDelay(10 * 365, TimeUnit.DAYS)
            .setConstraints(
                Constraints.Builder()
                    .setRequiresCharging(true)
                    .build()
                )
                .build()
        )
    }

And then make sure to call enqueueDelayedWorker() whenever you enqueue the Worker for your app widget.

That's correct. It's a WorkManager issue not related to Glance/RemoteViews but related to the AppWidget system behavior. As explained in the linked issue whenever WorkManager detects that no job is enqueued it disables it's onBoot provider. That causes the system to launch an onUpdate event to the widget receiver.Thus the flickering.

The solution should fix it, you should call it whenever you enqueue a worker, by using the KEEP policy it is safe to call multiple times. WorkManager handles the rest (e.g app restart, device restart, etc...)