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

Issue 760786 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Timeout waiting for [Responder Auth]

Project Member Reported by khorimoto@chromium.org, Aug 30 2017

Issue description

(Originally obtained from issue 760769.)

Usually, the time taken between sending the [Initiator Hello] and receiving the [Responder Auth] message is about 0.5-1s. We have a 5-second timeout, after which time we give up. It should not be common that we have a [Responder Auth] timeout. This is probably a Bluetooth issue.

device_to_device_authenticator.cc:198
Authentication failed: Timed out waiting for [Responder Auth]
15:08:30.283
secure_channel.cc:286
Failed to authenticate connection to device with ID CAESR...aUA==
15:08:30.283
bluetooth_low_energy_weave_client_connection.cc:188
Disconnection requested; sending "connection close" packet to {id: "CAESR...aUA==", addr: "73:66:3A:F8:09:EF"}.
15:08:30.283
bluetooth_low_energy_weave_client_connection.cc:675
Received invalid packet from {id: "CAESR...aUA==", addr: "73:66:3A:F8:09:EF"}. Sending a "connection close" uWeave packet.
 
Owner: mcchou@chromium.org
Status: Assigned (was: Untriaged)
Labels: -M-61 M-63
Moving to M-63 since this is not a common repro.
Status: WontFix (was: Assigned)
I haven't seen this issue in a long time, and a few months of Bluetooth stability fixes have come in. Closing out - we can reopen if necessary.

Sign in to add a comment