Issue metadata
Sign in to add a comment
|
SmartLock: Failed to parse key data: expected serialized_beacon_seeds |
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10032.86.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.140 Safari/537.36 Platform: 10032.86.0 (Official Build) stable-channel eve Steps to reproduce the problem: 1. Set up SmartLock, it works 2. Some time later it stops working, showing a green unlocked icon and no text input, click photo to unlock 3. Click photo to unlock, it blinks but does not log you in 4. Click on lock icon will provide the text input box, use your password and get in, open a bug. What is the expected behavior? Clicking the profile photo or hitting enter will log me in. What went wrong? Here are the proximity auth logs. I have no further details: 15:09:37.000 easy_unlock_key_manager.cc:160 Failed to parse key data: expected serialized_beacon_seeds. 15:09:39.113 easy_unlock_key_manager.cc:160 Failed to parse key data: expected serialized_beacon_seeds. Did this work before? Yes Chrome version: 63.0.3239.140 Channel: n/a OS Version: 10032.86.0 Flash Version:
,
May 11 2018
,
May 14 2018
Yes, it does appear to be working again on dev. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by jhawkins@chromium.org
, Feb 28 2018Owner: jhawkins@chromium.org
Status: Assigned (was: Unconfirmed)