nsmanagedobject

I have a custom NSManagedObject subclass, say, Person . I also have a UIView registered with -addObserver:forKeyPath:options:context: to observe various properties of a Person , some of which are persistent like "name" and others are just dumb KVO-compliant accessors unrelated to Core Data, like "drinking". @interface Person : NSManagedObject { BOOL drinking; } @property (nonatomic, retain) NSString* name; @property (nonatomic, readonly) BOOL drinking; @end @implementation Person @dynamic name; ... - (void) getDrunk { [self willChangeValueForKey: @"drinking"]; drinking = YES; [self

(self asking and self-answering because I spent hours on the web looking for this, and most of the resources all say "I solved it in the end" without giving an explanation) I had a very simple Core Data + Bindings application: An NSArrayController pulling items out of Core Data An NSTableView rendering them Another NSTableView that when you click on a row in the first table, displays the details of that item Item 3 above was causing application crash, with the error: [(my NSManagedObject) copyWithZone:]: unrecognized selector sent to instance Implementing that method (!) and putting a

I have a custom class, which is a subclass of NSManagedObject . I would like to store it in a dictionary, but when trying to do so I receive a Property list invalid for format: 200 error. Here is how I try to create the dictionary: NSDictionary *dictionary = [NSDictionary dictionaryWithObject: voiceMemo forKey:@"voiceMemo"]; Same result when trying NSDictionary *dictionary = [NSDictionary dictionaryWithObject: (NSData *) voiceMemo forKey:@"voiceMemo"]; It works, however, when trying to save the individual attributes separately: NSDictionary *dictionary = [NSDictionary dictionaryWithObject:

I have a really annoying problem, which I just can't seem to get fixed. I have a view when I send a message that gets saved to the Core Data, when thats done it asked the database for a random message (sentence) and saved that as well to an other row in the database. If I do the last part hardcoded, without fetching data from the DB, it works all fine and dandy, but as soon as I fetch the random row from the DB it goes crazy. In my AppDelegate.m: - (void)save { NSAssert(self.context != nil, @"Not initialized"); NSError *error = nil; BOOL failed = [self.context hasChanges] && ![self.context

I am working with CoreData, on an entity called "RoleName". The problem is: I click on "Create NSManagedObject subclass" from within my model, and so it automatically creates the classes for my entity. However, on the declaration of the class, I get this error: Invalid redeclaration of "RoleName" even though I don't have any other class with the same name. This is because Xcode handles all that by itself. I felt it like a bit of trouble as the auto generated classes don't have all my properties. So follow these steps to get this as it used to be: Delete what ever classes you already made for

I have really been stuck on this issue and I have referred to this stackoverflow post but my application still crashes with the issue: Failed to call Designated Initializer on NSManagedObject Class So, I have multiple entities and I have subclassed the NSManagedObject . Let's pretend I have entities named: FirstEntity, SecondEntity, ThirdEntity, Fourth Entity, FifthEntity. Let's also pretend I have two attributes named firstAttribute, secondAttribute in each Entity. I went into the xcdatamold opened up the editor and then selected create NSManagedObject Subclass for all of my entities. Then I

This is my NSManagedObject : @objc(Order) class Order: NSManagedObject { @NSManaged var orderItems: Set<OrderItem> //error: Cannot specialize non-generic type 'Set' } Anyone know why it doesnt work? OrderItem file is created and works however for following declaration: @NSManaged var orderItem: OrderItem Just for reference if someone should come to this question in the future for this nasty bug, since the discussion went on in the comments. Yes, the default Set type in Swift is generic, but in this case a custom non-generic Set class was shadowing the class defined by the language's standard