ARC issue, restarting bluetooth causes app to lose references to connected devices
Reported by
t...@samlabs.com,
Sep 4
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10718.88.2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.118 Safari/537.36 Platform: 10718.88.2 (Official Build) stable-channel reef-unibuild (electro basking pyro sand snappy alan bigdaddy) Steps to reproduce the problem: 1. Using Android bluetooth low energy API start a scan 2. Connect a device 3. Stop and restart the scan notice that the reference to the device is lost. What is the expected behavior? App should not lose reference to connected devices even when a new scan is started. What went wrong? In ChromeOS 68 and above (tested on 69 and 70 on beta and dev channels) when restarting a bluetooth low energy scan, any references to connected devices are lost. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 68.0.3440.118 Channel: stable OS Version: 10718.88.2 Flash Version: 30.0.0.134
,
Sep 5
,
Sep 6
Looking into this further it seems in ChromeOS 68+ when calling BluetoothLeScanner.startScan() we receive a onScanResult callback (https://developer.android.com/reference/android/bluetooth/le/ScanCallback.html#onScanResult(int,%20android.bluetooth.le.ScanResult) for every device that the system has cached in the session. This was not the behaviour in ChromeOS 67 and below.
,
Sep 19
I have also found that the scan returns stale devices, and filed https://bugs.chromium.org/p/chromium/issues/detail?id=885339 |
||
►
Sign in to add a comment |
||
Comment 1 by m...@samlabs.com
, Sep 5