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

Issue 895916 link

Starred by 1 user
Status: WontFix
Owner:
nohle@chromium.org
Closed: Oct 16
Cc:
█ jlklein@chromium.org
khorimoto@chromium.org
█ jordynass@chromium.org
█ jhawkins@chromium.org
hansberry@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Cannot setup Smart Lock using old flow

Project Member Reported by nohle@chromium.org, Oct 16 
Chrome version: HEAD of master (commit 804659abdf89d2528234201efd66d87681503551)

To reproduce,
1. Disable all "MultiDevice" flags
2. On phone, set EASY_UNLOCK_HOST supported (not enabled) and BETTER_TOGETHER_HOST not supported (and not enabled)
3. Go to chrome://settings/lockScreen, enter password, and click "Set up" (https://drive.google.com/open?id=1y1lWWwfo7itvY_QI_WEEQ-XRzvuABTHm)
4. Enter password on the lock screen (https://drive.google.com/open?id=1juHsfh4i3FrUcnU8Rkv9Aa9KNDjVFKWb)

I am taken back to the screen from step 3. Now, clicking "Set up" does nothing except each click logs "[...:WARNING:easy_unlock_app_manager.cc(84)] No extension". The flags on my phone stay the same as well: EASY_UNLOCK_HOST is supported but not enabled, even after forcing a device sync.

Although step 1 involves disabling all "MultiDevice" flags, once  https://crbug.com/895585  is fixed, some legacy users will still have access to the old setup flow even with these flags enabled. If this is not just a "me" problem, then this is blocking  https://crbug.com/895585 .

The attached logs start right before the first "Set up" click.
old_easyunlock_flow_logs
6.3 KB View Download

Comment 1 by khorimoto@chromium.org, Oct 16

Owner: nohle@chromium.org
The "No extension" error refers to the Smart Lock Chrome App. In the old flow, Chrome OS was packaged with a Chrome App built outside of Chromium; clicking that button would open the Chrome App.

You've built and deployed your own version of Chromium OS (not Chrome OS), but Chromium OS does not contain this packaged Chrome App; thus, when you click the button to start setup, no app can be found.

Please see if you can reproduce this issue on a build of Chrome OS (to make sure you're on the right one, look at the Chrome icon; if it is Google-colored, it is Chrome, and if it is various shades of blue, it is Chromium).

Comment 2 by nohle@chromium.org, Oct 16

Status: WontFix (was: Untriaged)
Thanks khorimoto@ and jhawkins@. After I set is_component_build=false is_official_build=true, and is_chrome_branded=true in gn args, it worked as expected. Sorry about that. Carry on :-)
►

Sign in to add a comment