Updating UI from Background Thread stops working after Navigating to a Page more than once

[MartinZikmund]

Discussed in #18178

^{Originally posted by ebondur September 10, 2024}
I am currently trying to update the UI of a page when an NFC read occurs. As monitoring the android device for NFC messages occurs on a background thread, the UI is updated from the background thread as well. When I first navigate to the page, everything works as expected. However, when I navigate away and back to the page, all UI updating stops. Here is the current behavior using a button to simulate NFC reads:

Example.mp4

Expected behavior is that The UI should update every time if the updates originate from the background thread, even if the page has been navigated to more than once. Only way to fix the issue is to close and reopen the app, which is not viable solution.

Sample Repo can be found here.

[Youssef1313]

Shouldn't UI updates be pushed through dispatcher when on background thread rather than updating it from the background thread? Does pushing to dispatcher make any difference?

[ebondur]

Using the dispatcher does not make any difference....

Could this be due to the generated models and data binding?

[ebondur]

Fwiw, I managed to devise a workaround via accessing the bindable model's ICommand for updating the UI. In the sample repo, this is on the Workaround branch.