Issue metadata
Sign in to add a comment
|
.startNotifications() fails when already notifying
Reported by
nallre...@gmail.com,
May 13 2017
|
||||||||||||||||||||||||
Issue descriptionChrome Version : 57.0.2987.146 Chrome OS Platform : 9202.64.0 What steps will reproduce the problem? (1) Connect to a device and start notifications for a characteristic (2) Disconnect from device, but never stop notifications. (3) Reconnect the device and call .startNotifications() (4) Observer the promise resolve with error "GATT operation failed for unknown reason." What is the expected result? On Mac OS, the promise simply resolves without an error. Should we expect consistency across platforms? Please provide any additional information below. Attach a screenshot if possible. The logs indicate that the promise was rejected because it was "Already notifying". Now that I understand this behavior it is easy to handle, but it wasn't immediately clear what was going on and is not consistent across platforms.
,
May 13 2017
> Should we expect consistency across platforms? Absolutely! We strive to make the experience across platforms uniform as it's one of the biggest advantages of the Web. It seems something in the underlying Bluetooth API (BlueZ) changed recently as we've been getting similar reports. See 719581 for example. Did you pair with the device by any chance?
,
May 13 2017
,
May 13 2017
I am able to use this code to reproduce the issue on my chrome book with a Parrot Mambo: https://github.com/NAllred91/ParrotConnectionText If you add catches on the startNotifications() promise and just ignore the error everything turns out fine, since the error is that we're already getting notifications.
,
May 13 2017
To be clear, the error that the promise rejects with is "GATT operation failed for unknown reason." The error that I observed in the chrome logs is "Already notifying".
,
May 15 2017
I'm failing to reproduce in Chrome 58. Could you update and give it another try?
,
May 15 2017
The only chrome book I currently have access to is this "acer chromebook 11". It says I am all up to date. I'm not sure if "Version 57.0.2987.146" refers to the chrome OS version or the chrome browser version? This is only an issue I've encountered on this chrome book(doesn't happen on my up to date Mac). So if you can't reproduce on a chromebook with version 58 this is probably a non-issue.
,
May 15 2017
,
May 15 2017
Chrome 58 was just released a couple of days ago so the update might not have reached all devices. You can try changing to a dev or beta branch: https://support.google.com/chromebook/answer/1086915?hl=en
,
May 16 2017
I'm now convinced this is the same as Issue 719581 . |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by nallre...@gmail.com
, May 13 2017