Fix sync Nigori cache GUID left empty upon mismatch
In the error-handling codepath where a mismatch is found on the cache GUID, when sync is starting for Nigori, the new cache GUID should be stored in the ModelTypeState. Otherwise, it would remain empty, which means the next sync start the mismatch detection doesn't take place. This can explain cache-GUID mismatches being ignored, and bad consequences such as violating the sync protocol by sending a non-empty progress marker despite the sync birthday being empty. Bug: 1063021 Change-Id: I05c1c000c17b1f10ff37984d1b8b9f812f02a7f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2111301Reviewed-by:Maksim Moskvitin <mmoskvitin@google.com> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#752085}
Showing
Please register or sign in to comment