Core Data's fetched property cause a crash on nested managed object context
| Originator: | kjh7232 | ||
| Number: | rdar://16605433 | Date Originated: | 14-Apr-2014 03:57 PM |
| Status: | Open | Resolved: | No |
| Product: | iOS SDK | Product Version: | 7.1 (11D167) |
| Classification: | Crash/Hang/Data Loss | Reproducible: | Always |
Summary: When I use fetched property from child managed object context, It causes exception that NSUnknownKeyException. Which reason is '[<_NSObjectID_64_1 0x145cb240> valueForUndefinedKey:]: this class is not key value coding-compliant for the key startDate.' It seams like $FETCH_SOURCE resolved as NSObjectID. and It causes a exception. Steps to Reproduce: 1. Create parent NSManagedObjectContext 2. Create child NSMangedObjectContext and set 'parentContext' property to parent NSManagedObjectContext 3. Use fetched property that has predicate with $FETCH_SOURCE Expected Results: $FETCH_SOURCE resolves as NSManagedObject and return right fetched property Actual Results: $FETCH_SOURCE resolves as NSObjectID and I got a exception and app crashes Version: 7.1 (11D167) Notes: Here is a exception: *** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<_NSObjectID_64_1 0x145cb240> valueForUndefinedKey:]: this class is not key value coding-compliant for the key startDate.' *** First throw call stack: (0x2edb8f03 0x3954dce7 0x2edb8c09 0x2f779ba3 0x2f6def39 0x2f6dee63 0x2f71d177 0x2f71cd53 0x2f71cb09 0x2f71c8f1 0x2f71be03 0x2eb0a199 0x2eb97df7 0x2eb9856f 0x39a3cb3b 0x39a36d3f 0x39a396c3 0x2ed83679 0x2ed81f45 0x2ecec7a9 0x2ecec58b 0x33c596d3 0x3164b891 0xef8fb 0x39a4bab7) Configuration: It occurs always on my iPhone 5, 5s which iOS 7.1 (11D167) installed. It occurs always on child NSManagedObjectContext. Attachments:
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!