Remove usages of IdentityManager::LegacySeedAccountInfo
It was required that |IdentityManager::LegacySeedAccountInfo| be called before calling |chromeos::AccountManager::UpsertAccount| because Chrome OS Account Manager's |Observer|s needed to translate |chromeos::AccountManager::AccountKey| to other formats (raw email and canonical email) and relied on |AccountTrackerService| / |AccountMapperUtil| for doing so. This is no longer required: - Chrome OS Account Manager can now maintain the mapping from AccountKey to email id by itself (https://crrev.com/c/1452003) and can notify its |Observer|s about this information (https://crrev.com/c/1477691). All new account additions to Chrome OS Account Manager are now guaranteed to have an email id associated with them in Account Manager itself. - AccountMapperUtil has now been deleted (https://crrev.com/c/1483024). Hence, remove the temporal coupling between |IdentityManager::LegacySeedAccountInfo| and |chromeos::AccountManager::UpsertAccount| in all production call-sites. This seeding of AccountInfo will now be handled within |ChromeOSOAuth2TokenServiceDelegate::OnTokenUpserted|, just after the account gets added to |chromeos::AccountManager|. Bug: 922026 Change-Id: I77cdaa93ef34fc400f00a09aee8d9d847ef0fc48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1495551Reviewed-by:David Roger <droger@chromium.org> Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Commit-Queue: Kush Sinha <sinhak@chromium.org> Cr-Commit-Position: refs/heads/master@{#638096}
Showing
Please register or sign in to comment