Quote:
Originally Posted by MileHiPhone
suzyq - I don't think this is a mobile me issue. I and others are having similar sync problems (there is another thread on those issues). I'm not sure what the reply post was trying to get you to do by turning off Mobile Me syncing - according to OF that is the easiest way to sync. I am trying the same set up and get the same errors and haven't been able to sync all day. Hang in there -- hopefully they will get this figured out quickly.
|
There's some confusing terminology here. If you go to your MobileMe preferences in System Preferences, you'll see that there's a feature which has MobileMe sync the contents of your iDisk from one machine to another (and to the MobileMe server). There is also the MobileMe webDAV service, which OmniFocus uses if you configure it to do MobileMe as your sync choice. OmniFocus writes directly to the MobileMe webDAV server, with no time lag. MobileMe disk syncing, on the other hand, runs periodically and tries to make sure that your files which are changed get replicated to the other MobileMe clients. The OmniFocus database is not a single file, but a whole directory full of them, even though the Finder treats it like a single file for many purposes. When MobileMe tries to reconcile changes made by OmniFocus directly on the server with an older copy on your local disk, bad things will happen to your data, because MobileMe has no clue how those files are organized, or how to protect against OmniFocus coming along and writing to those files as it is shuffling them around. The recommendation is that you not store your OmniFocus database in a part of the MobileMe disk structure that will be synchronized by MobileMe, if you use the MobileMe disk synchronization feature (many do not).
The bug that is being seen elsewhere appears to be triggered at least in some cases by the database file on the sync server (MobileMe's webDAV server, in this case) appearing to be more recent than the copy on the local machine. One way that could happen is if MobileMe tries to sync your database for you. My suggestion above eliminates the situation of the sync server's copy appearing newer by replacing it with the good local copy, and turning off MobileMe disk syncing eliminates that as a possible cause for the server's copy appearing newer. It does not guarantee that she isn't seeing this behavior for another reason, but it does eliminate one known cause.
So, I'm not telling her not to use MobileMe as her sync method for her iPhone, I'm telling her not to use something else also called MobileMe to potentially corrupt her database. There's a sticky at the top of the iDisk/MobileMe/.Mac syncing forum that talks about the discovery of the issue, labeled "Warning from OMNI: iDisk Sync can report false conflicts" if you want more info.