Status Update
Comments
za...@google.com <za...@google.com>
wv...@google.com <wv...@google.com> #2
Hello,
I'm only a little familiar with Power Apps. Is your app a mobile app or a web app?
This link
The primary
If your app does not work on Android mobile devices, you can also consider the
di...@gmail.com <di...@gmail.com> #3
di...@gmail.com <di...@gmail.com> #4
I'm not currently able to reproduce this using a sample project, at least on the emulator. In our main app, it looks like the mitigation is to wrap calls to "updateAll()" with a coroutine Mutex. There is something off with updateAll where it causes problems and doesn't always update the widgets correctly if it's not run inside a Mutex, even if it's being called with the Main dispatcher.
In those cases, we'll also sometimes see an entry such as "Work [ id=df621ec1-e37d-4d59-8e54-828b5234b2b4, tags={ androidx.glance.session.SessionWorker } ] was cancelled java.util.concurrent.CancellationException: Task was cancelled." in the logs (with no other stack trace).
Description
Version used: 1.1.0
Devices/Android versions reproduced on: Pixel 7/Android 14
Sometimes when Glance receives an update, it triggers a warning in the logs:
Work [ id=df621ec1-e37d-4d59-8e54-828b5234b2b4, tags={ androidx.glance.session.SessionWorker } ] was cancelled
java.util.concurrent.CancellationException: Task was cancelled.
Glance does not handle these cancellations and does not try to update the widget again, resulting in one of the widgets being stuck in a stale state.