Hi @korzonkiee ,

From what version are you trying to perform the update ? Note that there is an issue that it's not possible to perform firmware update with a Verity Sense while it's being charged before latest release 2.2.6 that fixed the issue, so the next firmware updates (if we make any) will work properly with charger. I'm wondering if this could be the issue for you right now ?

Hey @jimmyzumthurm

I was trying to update from 2.1.0. The device was not connected to charger during firmware update.

@korzonkiee Thanks for the information. So I don't see any reason why it would fail from the device side.

@samulimaa @R-Laukka @TeemuLauPolar Could any of you look into this ?

One of our users just experienced this issue on iOS SDK 5.8.0 with Polar 360 as well. After doing some investigation, it looks like after writing the firmware is finished (link), the device gets rebooted and when device reconnects, it tries to factory reset the device (link). However, it appears that sometimes the doFactoryReset method is invoked too early — before the PSFTP_MTU_CHARACTERISTIC becomes enabled — which causes the sessionFtpClientReady method from doFactoryReset to throw PolarErrors.notificationNotEnabled.

In the logs attached above, you can see that the FB005C51-02E7-F387-1CAD-8ACD2D8DF0C8 (PSFTP_MTU_CHARACTERISTIC) was enabled after trying to perform factory reset.

2024-11-01T12:58:52.230Z V [Polar SDK] [BLE] Session opened, deviceId: AD18CC2C
2024-11-01T12:58:52.230Z V [Polar SDK] [BLE] Performing factory reset while preserving pairing information
2024-11-01T12:58:52.238Z V [Polar SDK] [BLE] Factory reset initiated
2024-11-01T12:58:52.239Z V [Polar SDK] [BLE] Error during device reboot or factory reset: notificationNotEnabled
2024-11-01T12:58:52.239Z V [Polar SDK] [BLE][ERROR] Error during firmware update: notificationNotEnabled
2024-11-01T12:58:52.900Z V [Polar SDK] [BLE] GATT Base notifyDescriptorWritten for chr: FB005C51-02E7-F387-1CAD-8ACD2D8DF0C8 enabled: true err 0

One way to fix it is to update waitDeviceSessionToOpen such that it checks the device session state is sessionOpen and additionally check if FTP client is ready, e.g. via sessionFtpClientReady.

Or, to keep things clean, leave waitDeviceSessionToOpen intact and introduce new waitSessionFtpClientReady method that will similarly to waitDeviceSessionToOpen and use it in places that proceed FTP-requiring operations.

Fixed in #516

FLOW-60541. The Fix will be out in the next release.

This should be fixed in the latest SDK release 5.10.0.

Thank you, @samulimaa, for taking the time to look into this.

I am currently verifying whether the issue is resolved, but I'm having trouble locating the code that ensures the FTP is ready before any FTP operations are performed. Could you please point me to the part of the code that addresses this?