Re: [web-bluetooth] Discover "non-discoverable" beacons

APIs that scan for devices, like Android's and iOS's, may just be 
doing a non-standardized procedure, rather than than the standardized 
General Discovery procedure. Right now, the WebBT spec requires 
`requestDevice()` to do the standardized procedure, but it'd be 
straightforward to specify something else that ignores the 
Discoverable bits. I haven't yet figured out which behavior I prefer.

Nordic may just be working around a hole in the Android API: Android 
[provides the 
flags](https://developer.android.com/reference/android/bluetooth/le/ScanRecord.html#getAdvertiseFlags()),
 but not whether the AD packet was connectable. iOS, on the other 
hand, [provides whether the packet was 
connectable](https://developer.apple.com/library/ios/documentation/CoreBluetooth/Reference/CBCentralManagerDelegate_Protocol/index.html#//apple_ref/doc/c_ref/CBAdvertisementDataIsConnectable),
 but not the flags.

-- 
GitHub Notif of comment by jyasskin
See 
https://github.com/WebBluetoothCG/web-bluetooth/issues/141#issuecomment-123094060

Received on Monday, 20 July 2015 23:38:54 UTC