Quote:
Originally Posted by Paul Hoadley
I'm using 96165 under Leopard. Syncing with iCal produces to-do items whose due date is one day ahead of the due date for the task in OmniFocus. I assume this is a bug, and I've logged it. Is anyone else seeing this?
|
This is an iCal bug introduced in Leopard: the value in the database is actually a specific time on that date, and it's stored correctly in the central calendar database, but in timezones East of GMT iCal is assigning the wrong date to the value when it reads it from the database. (This also leads to bogus synchronization conflicts.)
We keep hoping Apple will fix it soon, but the workaround we're considering is to drop the time from the value and just publish the date. (That won't bother iCal, since it doesn't pay attention to the time anyway; but it would be an unfortunate loss for other clients synchronizing with the database, such as phones and other handheld devices.)