"Exit and childlock" breaks sign-in/sync state |
||||
Issue descriptionRepro steps: - Sign in to Chrome. - Create a supervised user (or sign in to a child account in another profile), so make the "Exit and childlock" option available. - In the first (non-supervised/child) profile, do "Exit and childlock". In the user manager, observe that the profile goes into a "signin error" state. Trying to unlock triggers a dialog "You were signed out of your Google Account. Sign in again to continue." After signing in again, the profile is unlocked, but the profile is still in a bad state (error icon in the profile menu), and Sync isn't working. After signing in yet another time, things work again, and future "Exit and childlock"s work as expected, without triggering the signin error state.
,
Oct 12
--Chrome Identity automated triaging-- This available, signin or profiles-related bug has gone at least 30 days since the last automated post without any further update. This bug will be closed out due to inactivity. Please re-open the bug and provide an update if it is still a valid or reproducible 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
,
Oct 12
Marc, is this issue still valid? I know we deprecated supervised users, so maybe okay to let this stay closed out?
,
Oct 15
I imagine the same might still happen if there's a Unicorn account? (I don't have any of those so I can't easily test it.) This wasn't really related to supervised users (or Unicorn) directly, just to the fact that their existence makes "Exit and Childlock" available.
,
Oct 15
I don't think that Unicorn accounts are launched for Chrome desktop yet? I'll keep this open for now, but decreasing priority to P3.
,
Oct 15
Right - AFAIK they're on Android and ChromeOS, neither of which have this kind of profile locking. TBH, given that a) the timeline for Unicorn-on-desktop is uncertain at best, and b) the sign-in/auth flows have changed so much that I'm not even sure this still applies, I'd probably just WontFix this for now, and re-evaluate if/when Unicorn ever launches on desktop. (Also, as a corollary, all the childlock code is dead for now, and you could consider just removing it all.)
,
Oct 15
SGTM :) |
||||
►
Sign in to add a comment |
||||
Comment 1 by sheriffbot@chromium.org
, Sep 13