cros: Migrate multidevice features to unconsented primary account
SplitSettingsSync will allow the user to opt-out of browser sync. However, IdentityAccessor::GetPrimaryAccountInfo() assumes the user has consented to browser sync. Multidevice features aren't tied to browser sync consent. Switch to using the "unconsented" primary account. On Chrome OS this account always exists for the logged-in user account, whether or not the user consented to browser sync. See go/cros-sync-mock and go/cros-primary-account for details. no errors in chrome://proximity-auth SplitSettingsSync, no errors in chrome://proximity-auth Bug: 1042400 Test: Multidevice setup works for new account with SplitSettingsSync, Test: Multidevice settings work for existing account with Test: updated chromeos_unittests Change-Id: I53171f3ba6a308c1af0da7a1092254e06f679bec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036786Reviewed-by:Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#738007}
Showing
Please register or sign in to comment