[Sync] Set signed in account before AndroidSyncSettings to match test expectations
Test expectation is that there is no signed in account at the beginning, and by the end of setUp test expects mAccount to appear signed in from AndroidSyncSettings perspective. It is done by calling updateAccount(mAccount) from setUp(). The issue happens when there is another signed in account according to ChromeSigninController.getSignedInAccountName, potentially left from some other test execution. The fix is to reset signed in account with ChromeSigninController.setSignedInAccountName before AndroidSyncSettings initialization. R=skym@chromium.org BUG=717960 Review-Url: https://codereview.chromium.org/2884953004 Cr-Commit-Position: refs/heads/master@{#472232}
Showing
Please register or sign in to comment