screen not updated during update process on Android with new architecture enabled

[sander48k]

In our App we show a progress bar for the device firmware upgrade process. On Android, when new architecture is enabled, the progress bar is not updated during firmware update. When new architecture is disabled, everything works as expected. On iOS there is no issue at all. Also, all other screen elements are properly updated in the Android App when the associated data changes. The only issue is with the progress- and state change of the mcu device upgrade.

To make sure this is not some issue specific to our App, I checked the example App of this library (current main branch). There, I see the same issue, i.e. the state and progress do not get updated in the Update screen during a firmware update. I have observed that the onProgress callback, passed to the Upgrade constructor in the useFirmwareUpdate hook is properly called when progress changes.

I've been looking for an explanation and solution for days but I am unable to find one. Therefor, although I can't imagine that the root cause lies in this library, I am asking you; Is this issue known to you? If so, do you have a solution or workaround?

[ball-hayden]

If it's getting through the native layers back to the JS onProgress callback, it's probably something to do with state management.

I wonder if it's being called sufficiently frequently that React/React Native is deciding to not re-render?

[sander48k]

I suspect there is an issue with changing state from within the JavaScriptFunction callback. I have submitted an issue to the expo project.

As a workaround I update the state outside of the callback function, using setTimout. E.g. in useFirmwareUpdate hook (example App):

const upgrade = new Upgrade(
  bleId,
  updateFileUri,
  {
    estimatedSwapTime: 60,
    upgradeMode,
    upgradeFileType,
  },
  (progress) => setTimeout(() => setProgress(progress), 0),
  setState
);

[ball-hayden]

Looks like that's been fixed upstream.
Thanks @sander48k!

Are you happy to close this issue here?

[sander48k]

Yes, fine with me. Thanks!