You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a push notification comes in, we enqueue a sync worker for the respective account. However, this worker will often not be executed immediately, depending on the priority of the push message, battery saving settings etc.
So we should probably do what Android apps are expected to do [1, 2, 3, 4] when a push notification comes in:
Enqueue a one-time sync worker.
Show a low-priority notification with some text like "Server-side changes pending".
If the user opens DAVx⁵ over the notification, the work will usually start because DAVx⁵ is in foreground. Alternatively, the worker may be as a background job at some time without user interaction.
As soon as the worker starts, it should remove the notification.
The text was updated successfully, but these errors were encountered:
When a push notification comes in, we enqueue a sync worker for the respective account. However, this worker will often not be executed immediately, depending on the priority of the push message, battery saving settings etc.
So we should probably do what Android apps are expected to do [1, 2, 3, 4] when a push notification comes in:
The text was updated successfully, but these errors were encountered: