This relates to MJ’s “Almost done” post earlier.
The actual problem was one of poor coincidental timing. I upgraded to 10.4.6, I started using Syncrospector, and I changed some code, all within a few hours of each other.
Syncrospector is a developer tool from Apple which allows great insight into the whole Sync process. I turned on some debugging info when I first started it. I then started running and debugging the code and started getting weird untraceable errors:
ISyncConcreteSession#pushChangesFromRecord:withIdentifier: - NSInvalidArgumentException - *** -[NSProxy forwardInvocation:] called!
failed to save the call history: NSInvalidArgumentException *** -[NSProxy forwardInvocation:] called!
I tried to track down this error, and eventually decided to switch on “Save call history very frequently” in Syncrospector’s preferences. This option comes with a warning about a performance hit of “catastrophic proportions”, which is why I hadn’t turned it on at this point. Sure enough, I got the above error a lot more times. The astute reader will think this obvious, but I hadn’t read the names of the preferences for Syncrospector, just the descriptions of what they did.
Turning off the call history saving made the error go away.
I’ll detail the other show-stopper bug in the next blog post, mostly because the information contained in each of these posts is good search engine fodder.