Exception in EncryptedStore.m about encrypted-core-data

[gavin-black]

I need to dig a little deeper into this, I've not had a chance to reproduce it yet. If you have a simple test case that fails that would help speed up the process.

[ert4i]

I will try to R&D and develope some simple project with this issue. But I've tried to use this library in ongoing big project and it failed as mentioned above.

[quarter1834]

Having the same problem here. I'll try to explain what we did.

First, we set up a one-to-many relationship in our data model, let's say we got a 'book' object and a 'page' object with such a relationship, so a book can have many pages and every page has exactly one book.
Now you create a book-object in your app and save the changes. Everything is fine. Then you go to another viewcontroller, fetch this book-object again from coredata, create one or more pages and try to set the book for the relation on every page-object or vice versa.
When you try to save now, the save operation will crash in the bindProperty:withValue:forKey:toStatement:atIndex: method after you test for [property isKindOfClass:[NSRelationshipDescription class]], because 'value' is not a managedObject but an NSSet which has no objectID selector.

Hope that helps to recreate the error.

Strange thing is that when you create the book-object and page-objects at once, the relationship will be saved correctly...

[gavin-black]

Quarter, are you seeing this on many-to-many relations only, or is it any sort of relationship? Still not reproduced it, but I think I have a general idea what's going on if it doesn't effect 1-to-1 or 1-to-many.

[gavin-black]

Closing this for now, it seems to be part of the many-to-many issue covered by #20