Unlock not working when there are multiple users signed in. |
||||
Issue descriptionIt seems that ProximityAuthSystem::OnFocusedUserChanged() gets called with an invalid user (EmptyAccountId). This cases the remote device life cycle to be destroyed. This call was triggered by ProximityAuthSystem::OnScreenDidLock(), which seemed to be triggered by https://cs.chromium.org/chromium/src/components/proximity_auth/screenlock_bridge.cc?q=ScreenlockBridge+package:%5Echromium$&dr=CSs&l=139 This was working before https://codereview.chromium.org/2861913002/, which removes the invalid account check from ProximityAuthSystem::OnFocusedUserChanged().
,
May 23 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9265ff00a94993e1db869cb7e540117102bc85d5 commit 9265ff00a94993e1db869cb7e540117102bc85d5 Author: sacomoto <sacomoto@chromium.org> Date: Tue May 23 21:34:54 2017 Do not destroy the life cycle when the user is invalid. BUG= 725142 Review-Url: https://codereview.chromium.org/2899803003 Cr-Commit-Position: refs/heads/master@{#474064} [modify] https://crrev.com/9265ff00a94993e1db869cb7e540117102bc85d5/components/proximity_auth/proximity_auth_system.cc
,
May 24 2017
,
Aug 1 2017
,
Jan 22 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by tengs@chromium.org
, May 23 2017