OTA BLE DFU doesn't work in Simplicity Connect 3.0.2

[pakara1]

OTA BLE DFU stopped working since version 3.0.2, while everything worked correctly in version 3.0.1. We use bootloader-apploader-inplace OTA DFU.
We also found that after scanning starts, the list of found devices appears much later than in version 3.0.1, and when the list then appears, it doesn't show Device Name content (UUID: 0x2A00), as it did in previous version 3.0.1.
Simplicity Connect is otherwise excellent and we use it extensively to update the firmware on our devices. Thanks for her!

[dellsala]

I've seen the same issues after upgrading from 3.0.1 to 3.0.2 (android)

• Discovered devices is much slower to appear.
• Device names do not get populated in the discovered device list.
• OTA DFU isn't working. I can initiate the OTA update from the main application, but after it boots into the OTA app, then connects, i see this error: "The attribute handle given was not valid on this server". It's like it hasn't refreshed the available GATT services for the OTA app, so it thinks the services required to perform the update aren't there.

[jolly-git]

I got OTA issue in android (on iOS OTA working fine)
Mobile: Samsung A55 with latest OS. App version: 3.0.2

[pakara1]

In version 3.1.1 Simplicity Connect OTA BLE DFU is working properly again! Thank you!