- From: Giovanni Ortuno via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Nov 2016 02:59:50 +0000
- To: public-web-bluetooth-log@w3.org
This seems like an issue with the Chrome implementation rather than a spec issue. In the future please use [http://crbug.com/new](http://crbug.com/new). The website you point to tries to scan for all the devices by generating a list of name prefixes and scanning for them. This causes devices with no name to be filtered out. Currently the Chrome Implementation only supports scanning for Service UUIDs and name/name prefix. iBeacon advertises Manufacturer Specific Data so for now there is no way to find it. The Spec does support filtering out by manufacturer data (and it even supports scanning for all devices) but that hasn't been implemented in Chrome yet. You can see a list of what's implemented in Chrome [here](https://github.com/WebBluetoothCG/web-bluetooth/blob/master/implementation-status.md#gatt-communication-api). -- GitHub Notification of comment by g-ortuno Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/335#issuecomment-260238011 using your GitHub account
Received on Monday, 14 November 2016 02:59:57 UTC