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

Issue 905005 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Hardlock state incorrectly reported to EasyUnlock.AuthEvent.Unlock

Project Member Reported by hansberry@chromium.org, Nov 13

Issue description

I've manually tested tapping the hardlock button on the lock screen, and then entering my password to unlock the device. Every time (5/5), EasyUnlock.AuthEvent.Unlock does not record "Password entry: User hardlock", but some other event, usually "Password entry: Phone authenticated". 

This logic being broken means that we don't have a good sense of whether or not users are tapping the hardlock icon regularly -- something we'd like to have a signal of in order to determine if the hardlock icon is confusing to users.
 
jhawkins@ mentioned that he may have removed some dead code in past CLs of his that was intended to emit this event (it would have been incorrectly plumbed, hence the appearance of being dead). That may a good place to start investigating this issue.
Labels: -M-72

Sign in to add a comment