You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to setup encrypted notifications using the GATT_CHR_PROP_ENCRYPT_NOTIFY characteristic property in my application, but it appears that when using the encrypted notify characteristic, notifications do not get enabled. When I just use GATT_CHR_PROP_NOTIFY, notifications are enabled and work totally fine. Within my code I am calling the following to setup notifications and register my callbacks for start and stop notify:
But instead with GATT_CHR_PROP_ENCRYPT_NOTIFY I just see:
DEBUG [Application] read <UUID>
I would also expect binc_application_char_is_notifying(app, SERVICE_UUID, CHAR_UUID) to return TRUE like it does when using unencrypted notifications, but it is returning FALSE when using encrypted notifications.
I have tested this on two separate devices, iOS and macos, and saw the same results.
Any help you can provide would be appreciated! Not sure if there is a step I am missing or if perhaps there is a bug here.
Thanks!
Kyle
The text was updated successfully, but these errors were encountered:
Hello Martijn,
I am trying to setup encrypted notifications using the
GATT_CHR_PROP_ENCRYPT_NOTIFY
characteristic property in my application, but it appears that when using the encrypted notify characteristic, notifications do not get enabled. When I just useGATT_CHR_PROP_NOTIFY
, notifications are enabled and work totally fine. Within my code I am calling the following to setup notifications and register my callbacks for start and stop notify:The encrypted read works fine and output is expected, but notifications are not being enabled.
In the debug logs I would expect to see the following as when using just
GATT_CHR_PROP_NOTIFY
:But instead with
GATT_CHR_PROP_ENCRYPT_NOTIFY
I just see:I would also expect
binc_application_char_is_notifying(app, SERVICE_UUID, CHAR_UUID)
to returnTRUE
like it does when using unencrypted notifications, but it is returningFALSE
when using encrypted notifications.I have tested this on two separate devices, iOS and macos, and saw the same results.
Any help you can provide would be appreciated! Not sure if there is a step I am missing or if perhaps there is a bug here.
Thanks!
Kyle
The text was updated successfully, but these errors were encountered: