"attempt to insert nil key" error

[David Strauss]

I have a fresh OS X 10.5.2 installation, and I'm trying to pull all address books back to my desktop from Zimbra 5.0.2 using the 5.0.1971 iSync connector. I get this error 123 records into the sync:

[Sat Feb 16 16:17:54 200] Caught exception while trying to sync: name = NSInvalidArgumentException, reason = *** -[NSCFDictionary setObject:forKey:]: attempt to insert nil key (1974)
[Sat Feb 16 16:17:54 200] cancelling sync (1974)
[Sat Feb 16 16:17:55 200] [assert] error: !contactErr
[assert] where: "ZimbraHelper_main.mm", "Sync", line: 1038
(1974)

[matthewhsu]

I am having the exact same problem. Running iSync connector 5.0.2 with Leopard 10.5.2. I've tried "Reset Sync Data" with both overwrite & merge options, to no avail.

Anyone know what the problem is?

- m

[David Strauss]

It's Bugzilla bug 24698.

[sculi2000]

The problem has been fixed. I believe it's bug 24949. The problem is that there is a malformed URL in one or more of the contact fields that is causing the exception. The fix will be in 5.0.3. Very sorry about the problem...I know it's annoying.

And I know the question...when will 5.0.3 be out? Unfortunately, I'm not in a position to precisely know that...I'll try and get someone here to post to this thread who can answer that.

Scott

[sculi2000]

To follow up on David Strauss's post...both 24949 and 24658 can cause exactly these types of exceptions, but it's more likely that what people are experiencing are malformed URLs. Regardless, both of the bugs are fixed.

Scott

[toddross]

Any update on when the fixed version will be released? Like several other users, I'm unable to use the sync feature until this is fixed.

[phoenix]

Originally Posted by toddross

Any update on when the fixed version will be released? Like several other users, I'm unable to use the sync feature until this is fixed.

You can always check bugzilla for the staus of a bug and the Product Portal for product releases and details will be in the Announcements forum. As you may have seen, 5.0.3 has been withdrawn because of an upgrade bug, the fixes for that and several other bugs will be in 5.0.4 and there's no release date for that yet (it should be soon, though).