Closed
Bug 995828
Opened 10 years ago
Closed 10 years ago
Cannot update Yahoo! calendars
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect)
Tracking
(blocking-b2g:-, b2g-v1.3T affected)
People
(Reporter: gaye, Assigned: gaye)
References
Details
(Whiteboard: [p=2], 1.3tarakorun2)
Steps to reproduce: 1. Open calendar. 2. Sync a Yahoo! calendar and note that all of your events get fetched. 3. Open calendar.yahoo.com. 4. Create a new event using Yahoo's calendar ui. 5. Go back to the calendar app. 6. Click the calendar's sync button. 7. Observe that your event is missing :(.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → gaye
Assignee | ||
Updated•10 years ago
|
blocking-b2g: --- → 1.3?
Assignee | ||
Comment 1•10 years ago
|
||
^^ Blocking a 1.3 blocker
Assignee | ||
Comment 2•10 years ago
|
||
So after some investigation, my diagnosis is that this is a bug in Yahoo!'s "ctag" (like etag but for calendars) implementation. I believe this because 1. I fetch a Yahoo! calendar with the calendar app by sending a PROPFIND to https://caldav.calendar.yahoo.com/dav/boot2gecko/Calendar. This returns https://gist.github.com/gaye/686909863e54703db0ed. 2. I log into Yahoo!'s web, calendar ui and create an event. 3. I hit the manual sync button which sends another PROPFIND to https://caldav.calendar.yahoo.com/dav/boot2gecko/Calendar. 4. I get the exact same xml response https://gist.github.com/gaye/686909863e54703db0ed. Since <CS:getctag>1-401</CS:getctag> has not changed and since the extension (see spec here http://svn.calendarserver.org/repository/calendarserver/CalendarServer/trunk/doc/Extensions/caldav-ctag.txt) states that the getctag property will change if changes (that clients should download) are made to my calendar, the calendar app rightly does not try to fetch updates from Yahoo! and does not do a REPORT.
Assignee | ||
Comment 3•10 years ago
|
||
Pinged my contacts at Yahoo! to see if they can reproduce and fix this on their side.
Comment 4•10 years ago
|
||
Confirmation from Yahoo:
> Yes, We are aware of a recurring issue with cache invalidation on couple
> of our hosts. Looks like it has happened again. This will be resolved in
> a day. Also, We are working on a better permanent fix, which might take few weeks.
Clearing the blocking flag on this one, leaving open to track until Yahoo is able to confirm a fix.
blocking-b2g: 1.3? → -
Assignee | ||
Updated•10 years ago
|
Whiteboard: [p=2]
Target Milestone: --- → 1.4 S5 (11apr)
Updated•10 years ago
|
status-b2g-v1.3T:
--- → affected
Whiteboard: [p=2] → [p=2], 1.3tarakorun2
Updated•10 years ago
|
Target Milestone: 1.4 S5 (11apr) → 1.4 S6 (25apr)
Updated•10 years ago
|
Target Milestone: 1.4 S6 (25apr) → 2.0 S1 (9may)
Assignee | ||
Updated•10 years ago
|
Target Milestone: 2.0 S1 (9may) → ---
Assignee | ||
Comment 6•10 years ago
|
||
Confirmed fixed.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•