nRF52 Failed to Discover a service, while nRF Connect could find it

[Karim_Os]

Hello all,

we faced a problem discovering a specific service while using SDK from (12 to 16) and devices (nRF52,nRF51)

the problem is that the peripheral responses with "Attribute Not found" when the central sends "find by type value request "

using nRF connect to the same peripheral it can discover the services successfully by sending "Read by Group type request" from the Mobile,

is there a way to control service discovery to be the same as nRF-Connect?

attached two screenshots from sniffing sessions of the two scenarios,

1- Connection using nRF connect

2- Connection using SDK_16.0

Thanks in advance

[Vidar Berg]

Hello,

Does your project include the Peer manager module (or support bonding)? If not, please check if the BLE_GATTS_EVT_SYS_ATTR_MISSING event is being handled in your application as shown by the MSCs here: GATTS System Attributes Handling: Unknown Peer. You can also take a look at the ble_app_uart example to see how this event handled.

Best regards,

Vidar