Handle response of not initialized sync token API.
If the password sync token API was not initialized (e.g. by in-session password change) token fetch on user online sign-in fails since the API returns an empty list of tokens. In order to fix this case we added token creation on first unsuccessful fetch attempt. As a result a valid token will be created on first password change or first online sign-in from any user device. Bug: b/173394869 Change-Id: Iacad53c1306a41f22749818ccd5d3d65b26e4d3a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2547296Reviewed-by:Denis Kuznetsov [CET] <antrim@chromium.org> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Commit-Queue: Maciek Slusarczyk <mslus@chromium.org> Cr-Commit-Position: refs/heads/master@{#829307}
Showing
Please register or sign in to comment