Improve UX for expired oauth tokens
Bug #1251028 reported by
Martin Albisetti
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu One Android Files |
Fix Released
|
Critical
|
Michał Karnicki | ||
Bug Description
Currently when an oauth token gets invalidates, there's no clear indication to the user that sync has permanently stopped, or a good way to fix your account.
We need the client to be smart about it and make it easy for the user to re-validate the client (without having to set up the whole client again!).
Related branches
| Changed in ubuntuone-android-files: | |
| assignee: | nobody → Michał Karnicki (karni) |
| Changed in ubuntuone-android-files: | |
| status: | New → Triaged |
| status: | Triaged → In Progress |
| Changed in ubuntuone-android-files: | |
| status: | In Progress → Fix Committed |
| Changed in ubuntuone-android-files: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| BLACKBERRY-ECD5 (gameovermylord-k) wrote | #1 |
To post a comment you must log in.
Currently when an oauth token gets invalidates, there's no clear indication to the user that sync has permanently stopped, or a good way to fix your account.
We need the client to be smart about it and make it easy for the user to re-validate the client (without having to set up the whole client again!).