[web-bluetooth] Device unable to connect in same browser environment (#668)

seanflynn5 has just created a new issue for https://github.com/WebBluetoothCG/web-bluetooth:

== Device unable to connect in same browser environment ==
Hello,

I'm facing a peculiar issue and am not sure exactly where the problem is but will try and give as much detail as possible. I use the Web Bluetooth API as part of an SDK to create connections between my company's devices and our customer's web apps. We received details from a customer that they're unable to connect to a certain model of device in Google Chrome on a MacBook, but I am unable to replicate the issue in the same browser environment on a similar machine. What I've noticed on my end is that when the device pairing prompt appears, it sometimes is initially listed as an unsupported device:

<img width="584" height="585" alt="Image" src="https://github.com/user-attachments/assets/743ec5ec-74c3-4b77-a90b-ca48bb9c360c" />

That circled MAC address corresponds to the one on my device. Eventually, after some time, that same devices updates with the actual device name:

<img width="599" height="532" alt="Image" src="https://github.com/user-attachments/assets/d68b7925-e2bb-426e-9f58-26fb25976b1d" />

Sometimes, if I try to connect when the MAC address is showing, I experience a connection failure like the customer is describing, but if I start a new session and wait for the option to be updated with the actual device name, it remedies the issue and the connection is successful.

What is peculiar is when the customer demoed their problem for me, the device showed the MAC address and never updated even after waiting for several minutes, AND the MAC address shown in the selection prompt did not match the one shown on the customer's device.

I realize there are a lot of factors at play here, so if I can provide any more information that would be helpful, please let me know. The latest suggestion I had for the customer was to try and clear their browser cache in case some incorrect data related to the device is somehow persisted, but I haven't heard if this helped at all yet. It's difficult to pinpoint the source of the issue but am receptive to any suggestions or ideas. Thanks!

Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/668 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 5 February 2026 21:27:02 UTC