Hook up ProximityAuthSystem in EasyUnlockService.

chrome/browser/signin/easy_unlock_app_manager.cc

Index: chrome/browser/signin/easy_unlock_app_manager.cc
diff --git a/chrome/browser/signin/easy_unlock_app_manager.cc b/chrome/browser/signin/easy_unlock_app_manager.cc
index 62bdf66948174e1af899c59f64c9f7e712176aa3..403684b42bbe9144c3647e2373a8aeabed78c892 100644
--- a/chrome/browser/signin/easy_unlock_app_manager.cc
+++ b/chrome/browser/signin/easy_unlock_app_manager.cc
@@ -90,6 +90,12 @@ void EasyUnlockAppManagerImpl::LaunchSetup() {
 }
 
 void EasyUnlockAppManagerImpl::LoadApp() {
+  // TODO(tengs): This is here temporarily to suppress the app background page
+  // until we completely replace it with ProximityAuthSystem.
+  if (base::CommandLine::ForCurrentProcess()->HasSwitch(
+          proximity_auth::switches::kEnableBluetoothLowEnergyDiscovery))
+    return;

[sacomoto, 2015/09/30 16:46:40]

The setup app doesn't load without loading the background app. Do you know why?

[sacomoto, 2015/09/30 17:40:53]

Ok, I found the issue. The background app registers an observer to launch the
paring_dialog:

https://cs.corp.google.com/#piper///depot/google3/googleclient/chrome/proximi...

Maybe remove this, and change the background.js not call |initEasyUnlock()|. We
can hide everything behind the BLE discovery flag
(userInfo[0].bleDiscoveryEnabled). 

[Tim Song, 2015/09/30 19:13:39]

Okay, I removed this check.

[Tim Song, 2015/09/30 19:13:39]

Acknowledged.

+
   ExtensionService* extension_service = extension_system_->extension_service();
   if (!extension_service)
     return;