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

Issue 757832 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

EasyUnlock v2: Timing out in the "signing in..." step for the lock screen.

Project Member Reported by sacomoto@chromium.org, Aug 22 2017

Issue description

In the lock screen, we correctly find the phone and authenticate it.

After I press enter the lock screen shows "signing in..." for a
while, and then times out. It seems that the |ChromeProximityAuthClient::FinalizeUnlock| never actually finishes.

This doesn't happen very often. It seems to happen when I keep locking and unlocking the screen.

The full logs are here:

-----------------------------------------------------------------------

16:48:37.763
proximity_auth_system.cc:186

Creating RemoteDeviceLifeCycle for focused user:
{"account_type":"google","email":"sacomotosmartlock4@gmail.com","gaia_id":"104253985630965752975"}

16:48:37.764
remote_device_life_cycle_impl.cc:55

Life cycle for A0:91:69:28:41:E6 started.

16:48:37.765
bluetooth_low_energy_connection_finder.cc:85

Finding connection

16:48:37.765
bluetooth_low_energy_connection_finder.cc:182

Adapter ready

16:48:37.766
remote_device_life_cycle_impl.cc:111

Life cycle transition: 0 => 1

16:48:37.766
unlock_manager_impl.cc:159

RemoteDeviceLifeCycle state changed: 1

16:48:37.767
unlock_manager_impl.cc:427

Updating screenlock state from 0 to 2

16:48:37.790
bluetooth_low_energy_connection_finder.cc:190

Discovery session started

16:48:41.893
bluetooth_low_energy_connection_finder.cc:167

Generating EIDs for: 6A:88:6A:80:7A:2E

16:48:41.895
background_eid_generator.cc:70

Generated EIDs: [
  (1503411300000: 0xe130),
  (1503412200000: 0x112f),
  (1503413100000: 0x78a6),
  (1503414000000: 0xbf47),
  (1503414900000: 0x5d64),
]

16:48:41.897
bluetooth_low_energy_connection_finder.cc:173

Found a matching EID: 0x78a6

16:48:41.898
bluetooth_low_energy_connection_finder.cc:147

Connecting to device 6A:88:6A:80:7A:2E

16:48:41.899
bluetooth_low_energy_connection_finder.cc:244

OnConnectionStatusChanged: 0 -> 1

16:48:41.901
bluetooth_low_energy_connection_finder.cc:226

Stopping discovery session

16:48:41.904
bluetooth_low_energy_weave_client_connection.cc:188

Creating GATT connection with 6A:88:6A:80:7A:2E

16:48:42.987
bluetooth_low_energy_weave_client_connection.cc:486

Sending connection request message.

16:48:42.988
bluetooth_low_energy_weave_client_connection.cc:517

Writing 7 bytes.

16:48:43.010
bluetooth_low_energy_connection_finder.cc:244

OnConnectionStatusChanged: 1 -> 2

16:48:43.012
remote_device_life_cycle_impl.cc:111

Life cycle transition: 1 => 2

16:48:43.012
unlock_manager_impl.cc:159

RemoteDeviceLifeCycle state changed: 2

16:48:43.014
device_to_device_authenticator.cc:136

Sending [Initiator Hello] message.

16:48:43.014
bluetooth_low_energy_weave_client_connection.cc:517

Writing 203 bytes.

16:48:43.234
device_to_device_authenticator.cc:237

Received [Responder Auth] message, payload_size=326

16:48:43.254
device_to_device_authenticator.cc:165

Successfully validated [Responder Auth]! Sending [Initiator Auth]...

16:48:43.259
bluetooth_low_energy_weave_client_connection.cc:517

Writing 255 bytes.

16:48:43.280
device_to_device_authenticator.cc:210

Authentication succeeded!

16:48:43.280
remote_device_life_cycle_impl.cc:111

Life cycle transition: 2 => 3

16:48:43.281
unlock_manager_impl.cc:159

RemoteDeviceLifeCycle state changed: 3

16:48:43.285
proximity_monitor_impl.cc:200

  Rolling RSSI: -36

16:48:43.285
proximity_monitor_impl.cc:203

[Proximity] Updated proximity state: proximate

16:48:43.286
unlock_manager_impl.cc:239

Proximity state changed.

16:48:43.329
unlock_manager_impl.cc:188

Status Update: (user_present=0, secure_screen_lock=0, trust_agent=1)

16:48:43.330
unlock_manager_impl.cc:427

Updating screenlock state from 2 to 10

16:48:43.535
proximity_monitor_impl.cc:200

  Rolling RSSI: -36

16:48:43.786
proximity_monitor_impl.cc:200

  Rolling RSSI: -36

16:48:44.036
proximity_monitor_impl.cc:200

  Rolling RSSI: -36

16:48:44.223
bluetooth_low_energy_weave_client_connection.cc:517

Writing 178 bytes.

16:48:44.288
proximity_monitor_impl.cc:200

  Rolling RSSI: -36

16:48:44.538
proximity_monitor_impl.cc:200

  Rolling RSSI: -36

16:48:44.790
proximity_monitor_impl.cc:200

  Rolling RSSI: -36

16:48:45.038
proximity_monitor_impl.cc:200

  Rolling RSSI: -36

16:48:45.288
proximity_monitor_impl.cc:200

  Rolling RSSI: -36

16:48:45.540
proximity_monitor_impl.cc:200

  Rolling RSSI: -36

16:48:45.791
proximity_monitor_impl.cc:200

  Rolling RSSI: -36

16:48:46.042
proximity_monitor_impl.cc:200

  Rolling RSSI: -36

16:48:46.294
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.7

16:48:46.543
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.49

16:48:46.793
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.343

16:48:47.044
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.2401

16:48:47.294
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.1681

16:48:47.545
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.1176

16:48:47.796
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.0824

16:48:48.049
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.3576

16:48:48.298
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.5504

16:48:48.549
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.6852

16:48:48.799
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.7797

16:48:49.050
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.8458

16:48:49.221
unlock_manager_impl.cc:480

Finalizing unlock...

16:48:49.300
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.892

16:48:49.551
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.9244

16:48:49.802
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.9471

16:48:50.052
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.963

16:48:50.303
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.9741

16:48:50.554
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.9819

16:48:50.805
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.9873

16:48:51.057
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.9911

16:48:51.307
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.9938

16:48:51.558
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.9956

16:48:51.811
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.697

16:48:52.060
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.4879

16:48:52.310
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.3415

16:48:52.561
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.2391

16:48:52.810
proximity_monitor_impl.cc:200

  Rolling RSSI: -35.1673

16:48:53.012
unlock_manager_impl.cc:427

Updating screenlock state from 10 to 0

16:48:53.014
bluetooth_low_energy_weave_client_connection.cc:218

Disconnecting from 6A:88:6A:80:7A:2E
 
Okay, this is probably an issue on the Android side. The unlock request is sent here:

16:48:44.223
bluetooth_low_energy_weave_client_connection.cc:517

Writing 178 bytes.

then, 5s later the timeout is triggered:

16:48:49.221
unlock_manager_impl.cc:480

Finalizing unlock...

it doesn't seem any message was received in the meantime.
Status: Assigned (was: Untriaged)
Components: -UI>ProximityAuth
Components: UI>SmartLock

Sign in to add a comment