Currently, Chromium's signin code is accessible by consumers at startup before all refresh tokens have been loaded. Consequently, clients need to listen for the event of all refresh tokens having been loaded to know that the signin code is in a stable state.
The Identity Service should instead guarantee that it does not respond to consumers until its internal state is stable after startup. This will eliminate an edge case that consumers currently have to worry about.
Comment 1 by bugdroid1@chromium.org
, Jul 10 2017