[notifications] User should be notified when background polling stops working
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu UX |
Triaged
|
Medium
|
Paty Davila | ||
account-polld (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
buteo-sync-plugins-contacts (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
sync-monitor (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
In Ubuntu there are some background processes which use Online Accounts to connect to remote services and check if there are new notifications for the user. Currently, account-polld does this for GMail and Twitter, and other use-cases might popup later (especially when we integrate chat services into messaging-app).
The problem
===========
Authentication tokens cached in Online Accounts do expire, or can become invalid at any time (because the user changes his password on the server, for example). When that happens, it's not always possible for a background process to retrieve a new authentication token: sometimes the remote server requests some interaction with the user (typically for re-entering username and password, or to renew the permission for the app), and this task can be completed only by a process capable of displaying some UI.
In order not to disrupt the user experience, we opted (bug #1401859) not to display a snap decision when such a situation arises, but now the user will never know if he's not receiving notifications because there are simply no notifications to be displayed, or because the polling has stopped because of an account error.
summary: |
- User should be notified when background polling stops working + [notifications] User should be notified when background polling stops + working |
Changed in ubuntu-ux: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Paty Davila (dizzypaty) |
Status changed to 'Confirmed' because the bug affects multiple users.