bonding fail ,when advertise data includes 16 bit service UUID

[seonhwan]

Hi. 

I use ble_app_hrs example.

Environment is follows. 

 - PCA100040 , nRF52 DK

 - nRF SDK v17.0.2

 - Galaxy Note10 mobile Phone

Bonding process is always fail, when the example code is modified as below;

static ble_uuid_t m_adv_uuids[] =                                   /**< Universally unique service identifiers. */
{
    {BLE_UUID_HEART_RATE_SERVICE,           BLE_UUID_TYPE_BLE},
	//{BLE_UUID_BATTERY_SERVICE,              BLE_UUID_TYPE_BLE},
	//{BLE_UUID_DEVICE_INFORMATION_SERVICE,   BLE_UUID_TYPE_BLE}
	{0xFEE5,									BLE_UUID_TYPE_BLE}
};

What is a problem?

[Simonr]

Hi

How have you implemented this custom BLE service? We have a tutorial on how to add a custom BLE service to your project here on Github.

What part of the bonding process is it that's failing? Are you able to see any error codes return when debugging the applcation?

Best regards,

Simon

[seonhwan]

Thank you for your answer. 

It is my a mistake. First bonding process is success and second bonding process is fail, because bonding data does not have erased in nRF52 DK.