Xcode CoreData Editor "Import" feature ignores "Ordered" option on Entities
| Originator: | john | ||
| Number: | rdar://21911975 | Date Originated: | 07/20/2015 |
| Status: | Open | Resolved: | |
| Product: | Xcode | Product Version: | 6.4 |
| Classification: | Reproducible: | Always |
When importing a .mom file into Xcode, the "Ordered" option is always set to False on the newly created relationships between Entities, even if they were True in the original model. Steps to Reproduce: 1. Install Xcode 2. Create a new iOS project with CoreData 3. In the CoreData editor, create a new entity with an ORDERED to-many relationship to another entity 4. Archive the app 5. From the app's archive, extract the .mom file 6. Create a new model version, and (optionally) clear its contents for clarity 7. With the CoreData Model selected in Xcode, choose Edit -> Import and select the .mom file you extracted earlier Expected Results: All of the entities should be recreated and the "ordered" field value should be maintained. Actual Results: All of the entities were recreated, EXCEPT the "ordered" field was not maintained. Version: 6.4 (6E3B5) / 10.10.4 (14E46) Notes: Aside from the obvious ramifications of assuming un-ordered data is ordered, this causes the hash-values to be different from previous versions, which causes the app to crash when migrating from a previous model-version. In other words, it causes newly updated apps to crash upon opening with a CoreData error. Configuration: Xcode 6.4, building for iOS 8.
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!