Forum >Replies by Nadeau Christian
Replies （6）
- You Reply: Hi Angelo,
We are using an apache cordova plugin (cross mobile platform framework). The problem is that any generic BLE plugins following the spec properly will try to write to this descriptor in order to enable notifications. And since it's not there, it's totally right to stop the enable notifications process at this point, and prevent the call to (e.g.: android) gatt.setCharacteristicNotification.
if you use native code directly, you are right, you can bypass this check, but it's more a hack than the actual spec.
Is there any reason technical reason why this descriptor was "deprecated" ?
Thanks for your reply,
Christian - You Reply: Hi Angelo,
We are using an apache cordova plugin (cross mobile platform framework). The problem is that any generic BLE plugins following the spec properly will try to write to this descriptor in order to enable notifications. And since it's not there, it's totally right to stop the enable notifications process at this point, and prevent the call to (e.g.: android) gatt.setCharacteristicNotification.
if you use native code directly, you are right, you can bypass this check, but it's more a hack than the actual spec.
Is there any reason technical reason why this descriptor was "deprecated" ?
Thanks for your reply,
Christian - You Reply: Hi Angelo,
We are using an apache cordova plugin (cross mobile platform framework). The problem is that any generic BLE plugins following the spec properly will try to write to this descriptor in order to enable notifications. And since it's not there, it's totally right to stop the enable notifications process at this point, and prevent the call to (e.g.: android) gatt.setCharacteristicNotification.
if you use native code directly, you are right, you can bypass this check, but it's more a hack than the actual spec.
Is there any reason technical reason why this descriptor was "deprecated" ?
Thanks for your reply,
Christian - You Reply: Hi, we have the exact same problem using evothings cordova-plugin-ble for android. The service exposed with Notify property does not contain the 2902 descriptor:
{
"descriptors": [
{
"uuid": "2901"
}
],
"characteristic": "dfb1",
"service": "dfb0",
"properties": [
"Read",
"WriteWithoutResponse",
"Write",
"Notify"
]
}
According to Bluetooth specs, it should return 2902 descriptor in order to configure the notifications for this specific service:
https://www.bluetooth.com/specification ... ifications (core version 4.2, page 2229, table 3.10)
Thanks,
Christian - You Reply: Hi, we have the exact same problem using evothings cordova-plugin-ble for android. The service exposed with Notify property does not contain the 2902 descriptor:
{
"descriptors": [
{
"uuid": "2901"
}
],
"characteristic": "dfb1",
"service": "dfb0",
"properties": [
"Read",
"WriteWithoutResponse",
"Write",
"Notify"
]
}
According to Bluetooth specs, it should return 2902 descriptor in order to configure the notifications for this specific service:
https://www.bluetooth.com/specification ... ifications (core version 4.2, page 2229, table 3.10)
Thanks,
Christian - You Reply: Hi, we have the exact same problem using evothings cordova-plugin-ble for android. The service exposed with Notify property does not contain the 2902 descriptor:
{
"descriptors": [
{
"uuid": "2901"
}
],
"characteristic": "dfb1",
"service": "dfb0",
"properties": [
"Read",
"WriteWithoutResponse",
"Write",
"Notify"
]
}
According to Bluetooth specs, it should return 2902 descriptor in order to configure the notifications for this specific service:
https://www.bluetooth.com/specification ... ifications (core version 4.2, page 2229, table 3.10)
Thanks,
Christian