Closed joonaservald closed 6 months ago
Hello,
This is kinda by design. I updated the doc now, but even before it was saying that whan an error is received that's all you get. The state won't change. The state goes to .aborted
only when DFU was explicitly aborted using the controller.
We may think about changing that, but that would be a breaking change, I think.
DFU Bootloader version:
Device information:
Describe the bug During a firmware update with the library, I am running into a case where the update fails but the
DFUServiceDelegate
methoddfuStateDidChange
does not return theaborted
case. During this case, I was logging out both state updates fromdfuStateDidChange
and errors fromdfuError
, more on that below. I would expect that if the update fails for any reason, the state would change toaborted
or similar.Logs The state and error updates come in the following order:
dfuStateDidChange
update:starting
dfuStateDidChange
update:enablingDfuMode
dfuError
update:Error 4: Operation failed
logWith
update:Disconnected
After this, nothing. The last known
DFUServiceDelegate
state update wasenablingDfuMode
and notaborted
.