After hearing from many of you and reading reports around the web, we
think we have a pretty good understanding of the problems that have
begun with 10.5.2. Here's a rundown:
1) As promised by Apple, 10.5.2 fixes the notorious Leopard iCal bug
present in 10.5 and 10.5.1. Unfortunately that bug was replaced by a
new bug with nearly identical symptoms: calendar events don't show up
in iCal. I've reported this to Apple and they responded that it's a
known bug that they're working on. Of course, they weren't able to
provide a time frame for a fix. As with the last bug, this procedure
can provide temporary relief and cause the events to show up in iCal
* Quit out of iCal if it's open
* Delete this file:
(~ refers to your home directory.)
* Open iCal
* Wait a minute or two until it finishes "Upgrading Calendars"
Unfortunately it doesn't work for everyone. YMMV.
2) If you sync with .Mac, then you might be wrestling with sync
conflicts that never go away. This problem is affecting users of all
types of sync software, not just Spanning Sync:
Nothing but .Mac: http://www.macfixitforums.com/showflat.php?Board=leopard&Number=851189
It seems likely that this is also a new bug introduced by Apple and
hopefully they're investigating. In the mean time, this procedure
* On a computer with up-to-date calendar data, sync with Spanning
Sync. If a conflict window appears, resolve all conflicts in favor of
Spanning Sync and let it sync again. Wait for the sync to finish.
* On the same computer, open the .Mac pref pane, go to the Sync tab,
click Advanced..., Reset Sync Data..., "Replace calendars on .Mac",
and click Replace. Wait for the sync to finish.
* On all other computers, perform a sync with .Mac. You should get a
message about merging or replacing data on that computer. Be sure to
select "Replace data on this computer" (*not* "merge") and then click
the Sync button. This needs to be done soon, before the next scheduled
sync with .Mac occurs on that computer. If there are computers syncing
with .Mac that you can't reach for whatever reason, just unregister
them from the Advanced... window in the .Mac pref pane. That will keep
them from syncing and overwriting the clean data. When you eventually
sit down to that computer and sync, be sure to select "replace info on
this computer" as above.
Now whatever property that was stuck on .Mac should be flushed out and
hopefully the conflicts will go away. If that doesn't help, try the
same steps but do a "reset info on this computer" from our pref pane.
That would be a more complete (but lengthy) process.
3) Duplicate calendars. Typically the first sync (with anything, not
just Spanning Sync) after a 10.5.2 upgrade will result in duplicate
calendars. I'll spare you the links to other forums, but this is also
happening all over the place regardless of Spanning Sync. Luckily the
fix is simple: just delete the duplicate calendars. For some extra
safe mojo, delete the second duplicate in the list since presumably
the first one is the original. From what I've seen, the calendars
don't come back again after this. I hate to sound like a broken
record, but this is also likely a new Apple bug since it happens with
plain vanilla .Mac syncing.
For what it's worth, we absolutely hate that our customers have been
placed in a position where they're continually having to deal with
these problems and that we're put into a position where we have to
point fingers. If at all possible we will place workarounds to these
problems in the upcoming v1.2. To that end, please follow onto this
thread with your experiences with the above and any other information
that might help us or other users.