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. Change-Id: I48d4b35a61dd20f56c416779bee686e1d582606d Bug: 1063021 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2111090 Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Auto-Submit: Mikel Astiz <mastiz@chromium.org> Reviewed-by:Maksim Moskvitin <mmoskvitin@google.com> Cr-Commit-Position: refs/heads/master@{#751966}
Showing
Please register or sign in to comment