Issue metadata
Sign in to add a comment
|
bluetooth device not connecting
Reported by
wez....@gmail.com,
Nov 3 2017
|
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
Steps to reproduce the problem:
1. call global.navigator.bluetooth.requestDevice({ filters: [{ services: ['heart_rate'] }] })
2. select device
3. this.device.gatt.connect()
3. connect promise never resolves
What is the expected behavior?
promise resolves and connects to device
What went wrong?
Hangs
Did this work before? Yes unknown
Chrome version: 62.0.3202.75 Channel: n/a
OS Version: OS X 10.12.0
Flash Version: disabled
Sample code:
https://jsfiddle.net/vves/nar20q4f/6/
,
Nov 3 2017
,
Nov 6 2017
Reporter@ - Thanks for filing the issue...!!
Tried to call global.navigator.bluetooth.requestDevice({ filters: [{ services: ['heart_rate'] }] }) using dev tools console, but got an error as "Uncaught ReferenceError: global is not defined at <anonymous>:1:1".
Could you please provide a sample test file to test the issue from TE-end. If possible also please provide a screen cast or screenshot explaining the exact issue.
This will help us in triaging the issue further.
Thanks...!!
,
Nov 13 2017
sorry you just need to remove global.
so it would just be:
navigator.bluetooth.requestDevice({ filters: [{ services: ['heart_rate'] }] })
,
Nov 13 2017
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 13 2017
Thanks for the report! Would you mind providing some logs? Instructions at: https://www.chromium.org/developers/how-tos/file-web-bluetooth-bugs
,
Nov 13 2017
Also, what device are you using? That way we can try to reproduce the issue ourselves.
,
Nov 14 2017
,
Nov 15 2017
If possible, please provide a jsfiddle/jsbin or just raw .html file that does the minimum steps needed to reproduce the issue. For requestDevice if you use 'acceptAllDevices' it will be easier for testers/devs to reproduce.
,
Nov 30 2017
,
Nov 30 2017
,
Dec 18 2017
macbook pro running macOS sierra (10.12) Chrome 63.0.3239.84 (Official Build) (64-bit)
,
Dec 19
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 19
Closing this issue as it has been a year without getting the logs requested in #6 or the device information requested in #7. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by manoranj...@chromium.org
, Nov 3 2017