why does iOS show/read 'DFUTarg' after successfully performing a DFU?

[gsingh622]

Hello, I am using Nordic's iOS library to perform DFU in our app to upgrade firmware on some BLE devices. Before the DFU, the app scans it as "Paradevice", but reads it as "DFUTarg" after the DFU is complete. Now if we perform the DFU again via NRFConnect, it comes back to "Paradevice" normally. There was also one instance where AFTER the DFU, we waited a minute or so, and it came back to "Paradevice".

Is there a way to clear the BLE name cache or do I need to Implement any change at firmware end to get rid of BLE name cache issue.

**Note: The same thing happens even when using NRF Connect, so we know it can't be the app

Thanks In advance.

[run_ar]

I don't think there is much you can do about that. If you look at the documentation you can see they prioritize to use the gap device name. So for a known device it looks like iOS uses the gap device name even though the advertisement has another name. So you need to wait for the gap device name to be updated. I think they would normally do that after a service discovery procedure.

[gsingh622]

Hey, thank you for the timely response; however, we do see the same issue using NRF Connect. We sampled 10 beacons ; 4 of which displayed the issue post-DFU where the units failed to start application Do you have any tips in this case?

Thanks in advance

[run_ar]

nRF connect on pc i presume? Anyway, if the device fails to start the application that is a totaly different issue than name caching. Can you verify that DFU finished succesfuly? i.e. prior to booting the application that is.

[gsingh622]

Yes on PC; and we ruled out the fact that if could be a non-finished DFU because half the time, we perform the DFU and it advertises it's proper name again, the other half; it says "DFUTarg" , with the same code that we examined and didn't change in both experiments

[run_ar]

I am sorry for the late answer. Which SDK version are you working with? It would be nice to know so I can check the known issues list for that sdk. sdk 12 issues, sdk 13 issues and sdk 14 issues