GitLab

The way ProfileSyncService determines whether the user is signed in
depends on refresh tokens being loaded, for secondary accounts.

This means, DISABLE_REASON_NOT_SIGNED_IN can report false positives
during startup, and should not be honored to clear sync metadata, until
refresh tokens are loaded and the signed-out state is determined
reliably.

This fixes cache GUIDs being reset upon every restart for secondary
accounts.

Bug: 955989
Change-Id: Ia149a940046da544f16c18d90cc5b5435c8968f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1782805Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#693121}