The following forum(s) are migrating to a new home on Microsoft Q&A (Preview): Developing Universal Windows apps!

Ask new questions on Microsoft Q&A (Preview).
Interact with existing posts until December 13, 2019, after which content will be closed to all new and existing posts.

Learn More

 none
BluetoothLeDevice GattCharacteristic Configure descriptor Indicate RRS feed

  • Question

  • Hi,

    I have a working bluetooth LE UWP application and I have come across what I believe is a Windows 10 issue with the setting of a characteristic notification. I have reproduced the exception on alternative store BLE scanner apps.

    Using the characteristic of Service Changed (0x2A05) (permissions set to Indicate only) from Generic Attribute Service (0x1801) I am trying to set up notifications on this characteristic in order to listen to a nordic device. 

    The code of WriteClientCharacteristicConfigurationDescriptorAsync(GattClientCharacteristicConfigurationDescriptorValue.Indicate) always throws exception of Access Denied 8007005.

    I can successfully turn on this indication via Android but not via UWP Windows SDK 1803. In UWP, I can successfully use the above function to set up notifications using GattClientCharacteristicConfigurationDescriptorValue.Notify. These always succeed.

    Is there any known issues related to the enabling of characteristic notifications which are Indicate only or anything relating to the public Service Changed characteristic??

    Best Regards,


    Matt

    Friday, November 15, 2019 2:03 PM

All replies

  • Hi,

    I tested with  BLE scanner store app, I could find available ble device in the app's device list. And I also check WriteClientCharacteristicConfigurationDescriptorAsync  method that required bluetooth capability, have you add this capability to your app?

    By the way, We invite you to post new questions in the "Developing Universal Windows apps" forum’s new home on Microsoft Q&A (Preview)!


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.


    Monday, November 18, 2019 2:09 AM