All of my events are in the Pacific/Auckland timezone in iCal, but
when I sync with Google calendar some of the events are moved about 22
hours forwards... eg an appointment at 12pm on Friday will be moved to
10am on Saturday. Bizarrely Google Calendar still reports the
recurring event as happening on Friday: eg "Weekly at 12pm on Friday",
but the event appears on Saturday with the time and date being
Saturday.
Google Calendar is also set to NZ timezone.
Regards,
Stephen
Thanks for the report. We found and fixed this bug yesterday, but your
events may have already been affected. (The bug was converting GMT+xx:
00 datetimes to GMT-xx:00 datetimes in some cases, so the farther west
you are from Greenwich, the bigger the error.)
If both iCal and Google Calendar are showing the incorrect time,
you'll need to restore one or the other from your backup or manually
change the affected events. If you fix the events in iCal, you should
then do a server reset ("Reset", "Info on Google Calendar"). If you
fix the events in Google Calendar, do a client reset ("Reset", "Info
on this computer").
Please post here if you run into any problems.
Thanks,
Charlie
/etc/localtime Sun Feb 18 01:59:59 2007 UTC = Sat Feb 17 23:59:59
2007 BRST isdst=1
/etc/localtime Sun Feb 18 02:00:00 2007 UTC = Sat Feb 17 23:00:00
2007 BRT isdst=0
Every appointment that I have before that date gets 1 hour less in
Google Calendar when compared to iCal whenever I sync. I can make sure
the time is correct in GCal, Reset the events in my computer, and the
same events appear on iCal an hour later.
Cheers,
Helvécio
On Feb 7, 1:03 pm, "cwood" <charlie.w...@gmail.com> wrote:
> Stephen,
>
> Thanks for the report. We found and fixed this bug yesterday, but your
> events may have already been affected. (The bug was convertig GMT+xx:
Regards,
Jim
I've just set up 1.0b14 having never installed any prior version. My
initial sync appears to have gone smoothly with this one exception: I
have one public Google calendar that only I can create events on. It
contains an event that occurs from 7:30 to 8:30 p.m. on the first
Sunday of every month, with no end date. This was imported into iCal
perfectly, but then in gCal every occurrence was moved to the Saturday
immediately preceding the originally scheduled date (times were still
correct). In editing the event details, it still showed the correct
Sunday recurrence, despite appearing on Saturdays. The Google calendar
is set to Eastern time, for the record.
In gCal I changed the date for the instance that was showing up on
Feb. 3rd back to the 4th, but in returning to the calendar it had no
effect. I edited that instance again and turned off recurrence, again
setting the date back to the 4th. Returning to the calendar, the date
was updated correctly. I again turned on recurrence, then ran Sync
Now. I ended up with duplicate events in both iCal and gCal, but they
were appearing on the correct date and time. I deleted the first item
in iCal and synced again, and all now appears well.
Oh, if it's relevant, the iCal calendar is in a group.
Sorry this is kind of a roundabout report, but I hope it helps. So far
Spanning Sync is great and answers the need I've had for a long
time...
Thanks!
Ches Martin
The iCal information seems fine. However, my gCal recurring events
have been moved an hour earlier. After doing a reset to "Replace Info
on Google Calendar with info from this computer" once, events were
still appearing in different places. Similar to Jim above, resetting
twice seemed to do the trick... for all but one stubborn recurring
event. It still appearing an hour early in gCal. Resetting it again,
that particular recurring event was fixed, but now a different one
exists an hour early. That makes 3 syncs, and still the problem isn't
completely resolved.
Both gCal and iCal are central time (GMT -06:00), however, I'm not
sure about gCal and it's handling of DST. Any ideas?
josh
This behavior is due to a bug in the Google Calendar API. For more
details, see the discussion at:
http://groups.google.com/group/google-calendar-help-dataapi/browse_thread/thread/6908f69f0e0ab258/
We're in the process of building some error detection/correction logic
so this won't continue to affect our users. Once that's in place, a
final server reset should clear up the problems for good. I'll post an
entry to the blog when that fix is ready.
Regards,
Charlie
On Feb 18, 3:17 pm, "joshuada...@gmail.com" <joshuada...@gmail.com>
wrote: