unable to unlock device with smart unlock. |
||||
Issue descriptionChrome OS 11151.17.0, 71.0.3578.27 Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1)Enable Better Together (2)Wait for sync and lock the device (3)Try to unlock device with smart unlock Expected Result: Actual Result: unable to unlock device with smart unlock. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) What is the impact to the user, and is there a workaround? If so, what is it? Please provide any additional information below. Attach a screen shot or log if possible. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Oct 31
Over to Ryan for initial triaging.
,
Oct 31
Hi Ansar, First, can you please clarify how this issue manifests? I suspect that when you lock the screen, you can at least see the Smart Lock icon next to the password field. Is that correct?. If so, does hovering your mouse over the icon provide any information via a tooltip? The logs of your feedback report include the line: "Updating screenlock state from [phone locked and rssi too low] to [phone not lockable]". This suggests to me that your phone does not have a lock screen -- is that correct? If so, setting up a lock screen on your phone (e.g., a PIN or Pattern to unlock) should resolve your issue (please confirm). Thanks, Ryan
,
Nov 1
Thanks Ryan, after enable PIN on phone, i can unlock the device with smart lock.
,
Nov 1
Hi Ansar, Glad to hear that helped. While you were having this issue, did your Chromebook display the following text? [1] (It's a bug if it did not): "To keep your Chromebook safe, Smart Lock requires a screen lock on your phone." Even if this is displaying correctly, it's possible we may need to adjust this string to be more explicit. 1) https://cs.chromium.org/chromium/src/chrome/app/chromeos_strings.grdp?type=cs&q=IDS_EASY_UNLOCK_SCREENLOCK_TOOLTIP_PHONE_UNLOCKABLE&sq=package:chromium&g=0&l=3634
,
Nov 1
No i didn't see that message.
,
Nov 1
I just reproduced this scenario on 11151.17.0 (as well as HEAD), and confirmed that the message "To keep your Chromebook safe, Smart Lock requires a screen lock on your phone" does correctly show. I suspect real issue at hand here is the significant latency of Smart Lock (it took over 10 seconds for the message to display while the Chromebook scanned for my phone) leading to a confusing user experience. It's also possible you clicked anywhere else on the screen, dismissing the tooltip message before getting a chance to read it. Even though everything seems WAI here, the UX could clearly be improved -- at the very least, we have plans in the future to improve latency. Hopefully the UI can be revisited as well. Closing as WAI. |
||||
►
Sign in to add a comment |
||||
Comment 1 by abod...@chromium.org
, Oct 30