Quote:
Originally Posted by Kelsangnorbu
The sound suggests absolutely nothing will be done, like the program/system isn't even trying to carry out the sync. Its more like an instant *no! you can't!* kind of noise. Rather than syncing being complete and nothing showing, its seems as though syncing never starts and therefore nothing changes in iCal.
|
Yes, that sounds exactly like what's happening. (If for some reason we're unable to start a sync session, we play the system alert sound. We play a different sound when we synchronize successfully.)
Quote:
Originally Posted by Kelsangnorbu
Hi Ken - there seems to be no change when I try to sync in the console log.
|
It sounds like we need to add some more diagnostics to our synchronization process, then, so we can have some clue as to what's failing. If you haven't already reported this to our tech support ninjas by sending email to
omnifocus@omnigroup.com, I highly recommend doing so now so they can start tracking this to make sure it gets resolved. (We do try to monitor the forums, obviously, but it's a lot easier to track email messages.)
Quote:
Originally Posted by Kelsangnorbu
I thought I'd include what it says when I start OmniFocus cos it's whinging about something it can't do:
===== Saturday, 2 June 2007 12:59:11 Europe/London =====
2007-06-02 13:00:10.707 OmniFocus[412] Can't open input server /Users/norbu/Library/InputManagers/Edit in WriteRoom
2007-06-02 13:00:10.897 OmniFocus[412] <TaskElapsedDateController: 0x11d8cf0>: Setting limit date of 2007-06-02 15:00:10 +0100 with predicate blockedByFutureStartDate == 1 AND effectiveDateToStart < CAST(202485610.895825, "NSDate")
|
This doesn't really have anything to do with iCal synchronization, but if you're curious:
The "Edit in WriteRoom" message is apparently caused by failing to load the WriteRoom input manager, but I don't know anything about that since I don't have that third-party input manager. (Maybe you had it installed, but then removed some part of it that it was using without removing this last piece from your InputManagers folder?)
The "Set limit date" log message is a debugging message in our start date scheduling code and doesn't indicate a problem (other than that we forgot to turn it off in non-debugging builds).