[DeviceSync v2] Schedule a first-time v2 DeviceSync
If a v2 DeviceSync has never successfully completed and there are no pending failure retries, schedule a first-time initialization sync. Previously, we were waiting for an InvokeNext instruction after a v2 Enrollment or a GCM notification before scheduling the first v2 DeviceSync. This change ensures that Chrome OS starts using v2 DeviceSync as soon as the flag is enabled. Bug: 951969 Change-Id: I6ed5330029f943d3cf1ae07eefa9d88f965689f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116227 Auto-Submit: Josh Nohle <nohle@chromium.org> Commit-Queue: James Vecore <vecore@google.com> Reviewed-by:James Vecore <vecore@google.com> Cr-Commit-Position: refs/heads/master@{#753265}
Showing
Please register or sign in to comment