new services are not updated on a previousl bonded client

[clock_work97]

Hi,

I am using nRF52832 for my development and our project requires us to have a bare minimum security between a gatt server(nRF52832) and gatt client(Android mobile APP).

Hence we have chosen to go for the route where the gatt server(nrF52832) generates a 6 digit passkey and prints it over UART and we type the same passkey on the gatt client(mobile app) to confirm the pairing process.

Now I would like to come to my problem. I have paired my gatt server(nRF52832) with the gatt client (Mobile app) and my gatt server has three service, Service A, Service B and Service C. 

Now I have added an extra service "Service D" to the gatt server, hence our service table now looks like: Service A, Service B, Service C, Service D. 

When I connect to previously bonded client, I can still on see three service, Services A-C. The newly added service is not discoverable on the bonded client device. 

Although I have found that once I unpair the gatt server from the gatt client and initiate a new pairing request, the new service "SERVICE D" is discoverable.

Could someone tell me why this is the case? and how do I overcome this? Is there a way to overcome it without initiating a new pair request??

[Einar Thorsrud]

Hi,

You need to have the service changed characteristic. That should be enabled by default though, but just in case you can add CONFIG_BT_GATT_SERVICE_CHANGED=y (or at least ensure you have not set it to n). When this is in place, the Bluetooth stack should automatically notified peers about the changed service.

[clock_work97]

Thank you very much Einar Thorsurd, This also helped me understand the pairing and bonding section better