Closed
Bug 965923
Opened 11 years ago
Closed 7 years ago
[B2G][Calendar] When unable to sync with yahoo the user is given no error message on the account details page
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect)
Tracking
(tracking-b2g:backlog, b2g-v1.2 affected, b2g-v1.3 affected)
RESOLVED
WONTFIX
| tracking-b2g | backlog |
People
(Reporter: jschmitt, Unassigned)
Details
(Whiteboard: dogfood1.3)
Attachments
(1 file)
|
31.16 KB,
image/png
|
Details |
Description:
This is inconsistent with the google account page. Google gives a 'Unable to sync' message while yahoo does not.
Repro Steps:
1) Updated Buri to BuildID: 20140127004002
2) Go the calendar app, add a yahoo account
3) On a pc, go to yahoo.com
4) Change the password of the account sync'd to the Buri
5) Manually sync the calendar on the buri
6) Select the 'drawer' icon
7) Select the '+' icon
8) Select 'Yahoo' and observe
Actual:
No 'Unable to sync' message on the yahoo account page
Expected:
'Unable to sync' message displayed on the yahoo page
Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20140121004137
Gaia: 47049555282a9a01fb60d1e1421b57e2810c96f5
Gecko: 6f7dfe36ab6c
Version: 28.0a2
Firmware Version: V1.2-device.cfg
Notes:
Repro frequency: 100%
See attached: Screenshot
| Reporter | ||
Comment 1•11 years ago
|
||
Issue occurs on 1.2
Environmental Variables:
Device: buri 1.2 MOZ
BuildID: 20140127004002
Gaia: 539a25e1887b902b8b25038c547048e691bd97f6
Gecko: d10e1f965d0c
Version: 26.0
Firmware Version: v1.2-device.cfg
Comment 2•11 years ago
|
||
I believe this is expected - there's different auth protocols used here. One will allow syncing to continue to sync using persisted creds, where as the other one does not.
Updated•11 years ago
|
blocking-b2g: 1.4? → backlog
| Assignee | ||
Updated•10 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
Comment 4•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•