iOS compatibility with DFU

[sjerlhagen]

We use nRF52832 and SDK 17.0.2 and the buttonless secure bootloader without bonding. I don’t understand the below issue, does that apply to our solution ? There will be custom apps for ios and android. Are there any other security or compatibility concerns I should be aware of ?

github.com/.../documentation.md

Known issues

1. Since iOS 13.3 (?) devices with Legacy DFU that do not use bonding, but use direct advertising in DFU Bootloader mode cannot be updated anymore. The same applies to Android devices with latest security patches. The solution is to modify the bootloader on a device to use non-direct advertising, but in order to update devices that are already in production, older, not updated devices are required. Nothing can be done on the library side, as the iOS just stopped reporting such advertising packets.

[Vidar Berg]

Hello,

It is referring to our legacy DFU solution (pre-SDK 12.x.x), not the secure DFU implementation used in SDK 17.0.2. So, you should not be impacted by this issue. 

Have you enabled the service changed characteristic in your application. This will be needed to force a service discovery if you ever need to change the attribute table layout on your device. E.g. if you add a new BLE service in a future update.