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

Issue 899392 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Nov 1
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Smart Lock never turns on

Reported by samuelfu...@gmail.com, Oct 26

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 11021.56.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.76 Safari/537.36
Platform: 11021.56.0 (Official Build) beta-channel cave

Steps to reproduce the problem:
1. Set up Smart Lock 
2. Attempt to use Smart Lock after one password sign-in

What is the expected behavior?
Smart Lock would work

What went wrong?
I cannot set up Smart Lock properly. Going through all the steps never activates it. There's no lock icon on my password screen, whether it's my first unlock since reboot or my 5th. Even during the setup process, trying out Smart Lock does not work as Smart Lock does not activate. Turning bluetooth on and off on both the chromebook and the phone makes no difference.

Did this work before? Yes 

Chrome version: 70.0.3538.76  Channel: stable
OS Version: 11021.56.0
Flash Version:
 
Cc: jlklein@chromium.org
Components: -UI UI>SmartLock
Owner: jessejames@google.com
Cc: khorimoto@chromium.org nohle@chromium.org jhawkins@chromium.org hansberry@chromium.org jessejames@google.com
Owner: hansberry@chromium.org
Thanks for passing along, Omri! Ryan, can you check this out? It sounds a bit like the issue you already fixed in M70, but the failure to turn on entirely in is interesting. We should try to get some logs on this from samuelfultonreyes1@.
Status: Started (was: Unconfirmed)
I'm nearly certain this is b/118780334 (for external users, this is a bug on the phone that we recently discovered, and are sending out a server push to fix now). Jeremy, when should users expect this issue to resolve for them?
Yep, sounds right. It should be fixed within ~15 minutes. Worst case, maybe an hour or so. Once that happens, going through setup should work again magically :-). Apologies for the breakage and thanks again for filing this, Samuel! I see there's a busy thread on reddit that will be happy to have this fixed as well.
Status: Fixed (was: Started)
Closing as fixed. Please reopen if observed again.
Config change is live now too :-)
Should the fix be expected in a ChromeOS update later? I just tried to set up again and it's still broken.
It's actually flipping a server flag that affects some logic on your phone. Your phone should get the new value on its own within an hour or two, but if you really want to give it a shot now, you can try the trick of going to your dialer on your phone and typing *#*#checkin#*#*. Source: https://lifehacker.com/5719657/force-your-android-phone-to-check-for-a-system-update
Well how about that. Thanks, everyone.
Glad it's working again for you! Thanks again for the report!

Sign in to add a comment