GATT Error: Not supported BluetoothRemoteGATTCharacteristic.startNotifications
Reported by
morganra...@gmail.com,
Nov 22 2017
|
||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: 1. Change lines 2-3 in ble.js to know service & char ID of device that supports notifications 2. Load page via an http server 3. Click button and pair with device What is the expected behavior? BLE should subscribe and begin receiving notifications. What went wrong? Receive error. Uncaught (in promise) DOMException: GATT Error: Not supported. Examining BluetoothRemoteGATTCharacteristic.properties I see `notify: false` despite nRF Connect on Android seeing it set and accepting. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 62.0.3202.89 Channel: stable OS Version: Ubuntu 17.10 Flash Version:
,
Nov 23 2017
,
Nov 23 2017
,
Nov 30 2017
What platform were you testing on? The issue was filed/marked as Linux, which is unsupported. What type of device were you using to send notifications? There are devices successfully working with notifications now.
,
Dec 6 2017
Checking again for more information to help us diagnose this. See Comment 4.
,
Dec 6 2017
Sorry for the delay. Yes, this is on Linux, I didn't realize it was unsupported but it doesn't matter it was realized it was my fault. But it did bring up something interesting. As nRF Tools shows, there is only one Service being broadcast, but Chrome showed two. The issue was I used the incorrect of those IDs. Any know reason multiple variations on the same ID would be shown?
,
Dec 6 2017
Thank you for providing more feedback. Adding requester "ortuno@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
,
Dec 6 2017
,
Dec 13 2017
Thanks. Multiple services when not expecting them does sound odd. It may be a BlueZ issue. We'd need to confirm on ChromeOS where we have patched BlueZ to correct issues with it, or on another platform we support. It would help to know which device, and or if it reproduces on other platforms.
,
Dec 13 2017
It's a custom device running an nRF51822. I'll make a snapshot of the firmware available should anyone want to attempt testings. I'll also bring the device to work with me this week to test Windows.
,
Dec 13 2017
Thank you for providing more feedback. Adding requester "scheib@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
,
Dec 13 2017
Windows support isn't fully there yet. If you do test on Windows please use Chrome Canary and chrome://flags/#enable-experimental-web-platform-features Ideally you could test from Android, macOS, or chromeOS. Is there any chance your device was changing service IDs, etc, and that Bluez cached old data and returned both?
,
Jan 3 2018
,
Jan 9 2018
,
Jan 10
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
,
Jan 16
(6 days ago)
Pinging for an update. Any chance you've tested this on Windows. Since this issue was last updated we've shipped Windows support to stable. If you still have it a snapshot of the firmware would be helpful. |
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by fbeaufort@chromium.org
, Nov 22 2017