Issue metadata
Sign in to add a comment
|
PO2TS / SigninManager should internally guarantee that tokens are always loaded on their startup |
||||||||||||||||||||||
Issue descriptionCurrently, ProfileOAuth2TokenService's tokens are loaded via an external flow that differs across platforms and use cases. In at least one case that flow is never invoked ( crbug.com/749535 ). As a prerequisite to changing the Identity Service to delay startup until all tokens are loaded, we should first change the flow so that PO2TS/SigninManager internally guarantee that tokens are always loaded as part of their startup. We can then make the Identity Service change described in crbug.com/740117 without the potential for it to cause hangs in some use cases. Note that this change will be a behavioral change at least in the case described in crbug.com/749535 , so it is not just a refactoring.
,
Nov 7 2017
,
Nov 6
--Chrome Identity automated triaging-- This bug is Available and has gone one year without any activity. If another month passes without any activity, this bug will be closed out. Please provide an update with the latest status for this bug. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 20
This bug is still relevant.
,
Nov 30
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Nov 1 2017