iOS Docs need known issue with Ordered Relationships/inverse relationship

Originator:scott.corscadden
Number:rdar://13191471 Date Originated:2013-Feb-11
Status:Open Resolved:
Product:iOS Product Version:6.1
Classification:Crash Reproducible:Always
 
11-Feb-2013 02:16 PM Scott Corscadden:
We just got severely bitten by exactly the problems described here:

http://stackoverflow.com/questions/7385439/exception-thrown-in-nsorderedset-generated-accessors

which we had to work around by implementing the methods as described in a few of the answers. Using the @dynamic CoreData auto-generated accessors causes a SIGABRT when running on device.

It would appear that this has been known about since iOS 5.1 - and it would have been really helpful if this was listed in the known issues, as the workaround of implementing your own methods does appear to work (we have no idea how inefficient it is, but appears to work for our use cases.

11-Feb-2013 02:18 PM Scott Corscadden:
Might (I'm guessing? Wish I could see other originated issues) be a duplicate of 10114310

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!