[Pyobjc-dev] Possible bug in PyObjC bridge (SyncService)
Brought to you by:
ronaldoussoren
From: Mani G. <ma...@tu...> - 2010-04-29 15:21:53
|
Hello, Users of my app have been complaining of the following error: ValueError: NSInvalidArgumentException - *** -encodeInt:forKey: only defined for abstract class. Define -[NSArchiver encodeInt:forKey:]! It occurs in the following line of code: session.prepareToPullChangesForEntityNames_beforeDate_(entityNames, NSDate.distantFuture()) Where "session" is an ISyncSession object (http://developer.apple.com/mac/library/documentation/cocoa/Reference/SyncServicesFramework/Classes/ISyncSession_Class/Reference/Reference.html#//apple_ref/occ/cl/ISyncSession), and "entityNames" is a Python list of strings. Most of the time, for most users, this problem does not happen. But it seems like, for some people a different code path is being executed under the hood of SyncServices and this is happening. Not much to start with, but I am here to provide any more information as needed. This is a very serious issue for our user base and hopefully someone will be able to shed light on the issue, if it is indeed a PyObjC bridge matter. Thanks very much! Mani |