Obtaining permanent ID on child MOC causes crash
Originator: | krismarkel | ||
Number: | rdar://11478919 | Date Originated: | 5/18/2012 |
Status: | Closed | Resolved: | YES |
Product: | iPhone SDK | Product Version: | 5.1 |
Classification: | Crash | Reproducible: | Always |
Summary: If I have a NSManagedObjectContext that's the child of another MOC and I ask for a permanent ID for an MO that has a relationship to another MO, the app will crash when I try to save the MOC. Steps to Reproduce: 1. Open the attached project and run it on the device or simulator. (http://cl.ly/3z250P2s3B1r3Z1W2C3o) 2. Create a new MO with the "+" button. 3. Go into the detail view for the MO just created. 4. Tap the Do Work button. Expected Results: Some new MOs are created on a child MOC and saved. Actual Results: Crash when saving the MOC. Regression: Notes: If you tap the Other Work button, the app doesn't crash because it creates permanent IDs for both MOs.
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!
Resolved
This has been fixed in a recent beta of REDACTED.
Duped as 11484480