IOS nrfConnect issue with DFU

[vivek.spraxa]

I am using nrf connect app on ios , the device is getitng on device mode but it is not showing DFU button on it , but it is working when using android app of it

And when doing dfu using ios liberary on react rative app, we are getting this error

DFU state: CONNECTING
98d3db5e-35d2-4003-9…-fc749e7a9a6c:92442 DFU state: DFU_FAILED
98d3db5e-35d2-4003-9…5-fc749e7a9a6c:5221 Error: DFU Service not found
at createErrorFromErrorData (98d3db5e-35d2-4003-9…5-fc749e7a9a6c:4204)
at 98d3db5e-35d2-4003-9…5-fc749e7a9a6c:4156
at MessageQueue.__invokeCallback (98d3db5e-35d2-4003-9…5-fc749e7a9a6c:4702)
at 98d3db5e-35d2-4003-9…5-fc749e7a9a6c:4433
at MessageQueue.__guard (98d3db5e-35d2-4003-9…5-fc749e7a9a6c:4606)
at MessageQueue.invokeCallbackAndReturnFlushedQueue (98d3db5e-35d2-4003-9…5-fc749e7a9a6c:4432)
at debuggerWorker.js:80

[bjorn-spockeli]

HI Vivek, 

after flashing the hex files to nRF52 DK and I connected to it with a Samsung Galaxy S9 using nRF Connect. I do not see the Nordic Buttonless DFU service with my Android device, just an unknown service. Are you sure that you have added this service?

Best regards

Bjørn

[vivek.spraxa]

You have to follow the steps on the given file to active notification and for authentication it is accept any password. output.pdf

[bjorn-spockeli]

Hi vivek,

iOS devices may cache the GATT table based on the address of the peripheral to avoid performing the Service Discovery procedure on every connection. Instead it just assumes that the peripheral will have the same order of services as the last time. So when  you are modifying the GATT table of the peripheral by adding/removing a service, then the iOS device will still think its the same GATT table as before. THis is why the DFU service is not shown. 

This can be solved by issuing a Service Changed indication, see GATTS Service Changed.

After adding the Nordic DFU service to the GATT table you need to call sd_ble_gatts_service_changed to inform the central that the GATT table has changed.

Best regards

Bjørn 

[vivek.spraxa]

Do you have any example for it, i am using plugin on RN app for it - react-native-nordic-dfu or any other example

[BinderT]

Related question:
https://devzone.nordicsemi.com/f/nordic-q-a/50712/can-t-get-examples-to-run-correctly

[bjorn-spockeli]

No, but it should only be the matter of calling sd_ble_gatts_service_changed() after you have added the Buttonless DFU Service, which I am assuming that you do after one sends 0x000610 to the characteristic of your custom service. 

There should not have to do anything on the central side, only on the nRF side. 

[bjorn-spockeli]

BinderT:The suggestion that my colleague Edvin gave you, i.e. incrementing the BLE address of the nRF, should solve the issues related to GATT table caching. Alternatively you can call sd_ble_gatts_service_changed() to the BLE_GAP_EVT_CONNECTED case in ble_evt_handler() in main.c.
Note, this will cause the nRF to trigger service discovery on every connection, so this should only be added for ease of development and removed in production code.