Skip to content

Conversation

@YevgenStarikov
Copy link
Collaborator

Fixing the following NEW error: "this class is not key value coding-compliant for the key @count" for iOS 10+

Fixing the following NEW error: "this class is not key value coding-compliant for the key @count" for iOS 10+
@YevgenStarikov
Copy link
Collaborator Author

@razmara this PR to align with source code and fix error

@YevgenStarikov
Copy link
Collaborator Author

@razmara FYI current code looks:

NSMutableSet <NSManagedObjectID *> *objectIDs = [NSMutableSet set];

    void (^unionObjectIDs)(NSMutableSet *, NSSet *) = ^(NSMutableSet *objectIDs, NSSet *objects) {
        if (objects != nil) {
            [objectIDs unionSet:[objects valueForKey:NSStringFromSelector(@selector(objectID))]];
        }
    };

    unionObjectIDs(objectIDs,notification.userInfo[NSInsertedObjectsKey]);
    unionObjectIDs(objectIDs,notification.userInfo[NSUpdatedObjectsKey]);
    unionObjectIDs(objectIDs,notification.userInfo[NSDeletedObjectsKey]);

but I think it is OK to proceed with this PR

@sasan-soroush
Copy link
Collaborator

Thanks @YevgenStarikov.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants