New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 848096 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
█ jlklein@chromium.org
khorimoto@chromium.org
█ jhawkins@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Devices persisted to UserData should include software features and last_update_time_millis

Project Member Reported by hansberry@chromium.org, May 31 2018 
See https://cs.chromium.org/chromium/src/chrome/browser/chromeos/login/easy_unlock/easy_unlock_service_signin_chromeos.cc?type=cs&q=EasyUnlockServiceSignin::OnUserDataLoaded&g=0&l=467

When devices are fetched from UserData in EasyUnlockServiceSignin, it's assumed that they are EasyUnlock hosts because EasyUnlockServiceRegular::LoadRemoteDevices() only persists EasyUnlock hosts. This is potentially fragile. Other fields like last_update_time_millis should also be persisted.
►

Sign in to add a comment