navigator.bluetooth.requestDevice cannot filter device which advertise serviceUUID in SCAN_RSP
Reported by
mich...@mommosoft.com,
Jul 27
|
|||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1.2 Safari/605.1.15
Steps to reproduce the problem:
1. call navigator.bluetooth.requestDevice with filters:[ {services: [ uuid128] }]
What is the expected behavior?
filter out the BLE device
What went wrong?
nothing found
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: 67.0.3396.99 Channel: n/a
OS Version: OS X 10.13.6
Flash Version:
,
Jul 30
I don't know why the device is not being found, but the address is expected to be different on macOS. macOS does not provide the actual MAC address of LE devices.
,
Jul 30
,
Aug 1
Can you click on "Inspect" in chrome://bluetooth-internals and attach a screenshot of the services detected on the device?
,
Aug 2
Have in mind that I am advertising with white list. Service uuid is send only if scan request is made, because in advertising packet there is no free space for 128 uuid. It is filtered out by Android and iOS API.
,
Aug 2
it is a BLE device.
,
Aug 3
Hmmmm even if the UUIDs are in the scan request, the device should appear. We take both the regular adv. packet and the scan request into consideration when showing a device. Logs would be really useful! Instructions at: https://www.chromium.org/developers/how-tos/file-web-bluetooth-bugs |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by mich...@mommosoft.com
, Jul 27