After setup, Smart Lock can sometimes be slow to enable |
||
Issue descriptionRight after going through set up, other features are enabled fine, but Smart Lock can be stuck in a disabled state. This always resolves itself eventually, but I've seen Smart Lock be stuck in this state for up to 5 minutes. I've attached a screenshot of the state it's stuck in. I'm not sure what is actually happening here -- is it waiting for some kind of message from the server? multidevice_handler reports that Smart Lock's status at this point is kUnavailableInsufficientSecurity -- which doesn't make sense, because my phone has a lock screen. As I mentioned, this issue always resolves itself eventually -- after reproducing this issue a few times, it looks like it corrects itself as soon as a device sync occurs.
,
Oct 5
The phone is responsible for changing its EasyUnlock state from "supported" to "enabled" when the lock screen is set. If you're seeing kUnavailableInsufficientSecurity, it means that EasyUnlock has not yet enabled the EASY_UNLOCK_HOST field yet. This bug should probably be moved to Buganizer since it seems to be a GmsCore issue.
,
Oct 5
Yeah, if the phone did *not* flip that bit, Kyle's right. If it did, proactive syncs on the crOS side will fix this.
,
Oct 5
re: #1, how can I determine if the phone thinks Smart Lock is enabled?
,
Oct 5
You can check using the proximityauth test app whether it thinks EASY_UNLOCK_HOST is enabled.
,
Oct 5
I've confirmed via the test app that EASY_UNLOCK_HOST is not enabled on the phone when this issue occurs.
,
Oct 5
Ryan, do you mind grabbing a bugreport from the phone and filing a bug in buganizer for this? Is it always EasyUnlock that's the slow one? That's pretty strange because the Android-side code just goes through and enables all the features in the same way...
,
Oct 5
Sure thing, filed at b/117330912. Closing this as we continue investigation there. |
||
►
Sign in to add a comment |
||
Comment 1 by jlklein@chromium.org
, Oct 5