We've been getting sporadic reports of recurrences being moved by gCal
to a different startTime. This morning I was able to reproduce this,
but only intermittently:

- I created the following entry (using the API with raw HTTP requests):
<entry xmlns='http://www.w3.org/2005/Atom'
xmlns:gd='http://schemas.google.com/g/2005'
xmlns:gCal='http://schemas.google.com/gCal/2005'>
<gd:recurrence>DTSTART;TZID=America/Chicago:20061231T050000
DURATION:PT3600S
RRULE:FREQ=DAILY;INTERVAL=1</gd:recurrence>
- It showed up in gCal as beginning at 0400 local time, not 0500
- I verified that the calendar and my gCal "current timezone" were both
set to America/Chicago

- Then I tried to reproduce the problem using the exact same code, but
with a new startTime (same day, different time). The new event showed
up fine.

- So I ran the same code 10 more times (using a fresh session each
time), each time with an identical recurrence other than the startTime
hour.
- 2 out of 10 recurrences were offset in gCal by -1 hour. The other 8
were fine.

Note that I don't know if the 1-hour offset is a constant, or if it's
based on my timezone. One of our users reporting seeing events that
were set to occur in the MST timezone, even though he's in EST, and all
of his personal and calendar settings are set to EST. However, in each
of my 10 test cases, the calendar in question was listed in the
metafeed as having the same timezone: America/Chicago.

Anyway, this appears to be easily reproducible for me. Please let me
know if I can provide any more detail that will help you guys track
down the problem.

Regards,
Charlie


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Google 
Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to