07. April 2009 · 2 comments · Categories: Mac
I've seen quite a number of MobileMe sync problems over the last couple of months. Some items that I add/delete/modify in my calendar don't make the jump between laptop and desktop, or vice versa. It's completely intermittent and always works perfectly if I deliberately try to catch it out. This is extremely unhelpful of it, as it means I just can't trust my calendar on either machine to be correct.

Picture 7 
I've found a way to at least get things back in sync (as far as I can tell without doing an exhaustive comparison) though it remains to be seen whether it will actually stop things going wrong again. On all machines, open the iSync application, open its Preferences, then click the "Reset sync history…" button, and select "Merge" when asked. It might ask several times, for various types of sync data, with big spinny-arrow pauses in-between. You're putting yourself in the hands of MobileMe's sync algorithms here, so don't come crying to me if it makes your kettle fur up with scale and your cat leave home. I'll update this post as and when I determine if the more general problem is licked. Sadly my gut feeling is that it's too much to hope.

Update: Still been having problems and have been tearing my hair out. The recent OS X 10.5.7 update promises some sync improvements though isn't specific about what. I'm hopeful, but I won't know for a couple of months as it usually picks just one or two important items to not sync every now and then. Enough to keep me on my toes.

2 Comments

  1. The best bet when you’re having sync problems really isn’t to “merge”, but to take the latest copy from a desktop machine and replace ALL information in the cloud. Then let it propogate back down. Also, on each machine, you should reset the sync history. That is the real problem.

  2. Resetting the sync history is exactly what I did on each machine. I merged because I was aware that it has failed to pass data in both directions so neither machine had a fully correct set of data.

You must be logged in to leave a reply.