Skip to content
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.

+managedObjectKeysByPropertyKey does not support NSNull, despite docs #7

Open
ainopara opened this issue Apr 12, 2015 · 3 comments
Open

Comments

@ainopara
Copy link

replace all the
if (managedObjectKey == nil)
to
if (managedObjectKey == nil || [managedObjectKey isEqual:[NSNull null]])
will resolve the crash issue.

@jspahrsummers
Copy link
Member

It sounds like you've specified NSNull where it isn't allowed. Can you please share the actual code you're using?

@ainopara
Copy link
Author

Yes, I assign keys that not be used to NSNull.null. like
@"history": NSNull.null
Remove those null things will make it work again without modify the adapter.

@jspahrsummers
Copy link
Member

Ah, I see—it looks like the documentation for +managedObjectKeysByPropertyKey is incorrect. Sorry about that.

I'll update this issue to clarify the problem.

@jspahrsummers jspahrsummers reopened this Apr 14, 2015
@jspahrsummers jspahrsummers changed the title -[NSNull _fastCStringContents:]: unrecognized selector sent to instance +managedObjectKeysByPropertyKey does not support NSNull, despite docs Apr 14, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants