I agree that this seems to be a CloudKit-only bug.Take the Apple sample code at https://developer.apple.com/documentation/coredata/handling_different_data_types_in_core_dataModify as needed to use CloudKit and it breaks with this error:Fatal error: ###persistentContainer: Failed to load persistent stores:Error Domain=NSCocoaErrorDomain Code=134060 "A Core Data error occurred." UserInfo={NSLocalizedFailureReason=CloudKit integration requires that the value transformers for transformable attributes are available via +[NSValueTransformer valueTransformerForName:], return instances of NSData, and allow reverse transformation:Book: tintColor - Claims to return instances of UIColor}: file /Users/conrodi/Downloads/HandlingDifferentDataTypesInCoreData/CoreDataAttributes/AppDelegate.swift, line 22I've seen the same problem in other CloudKit projects. I think CloudKit is broken for Transformable Core Data attributes.
TallBassett
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Me too. Version 12.0 (12A7209). Delete and reinstall of Xcode did not help.
I did the same as Gerrit. My download called itself Version 12.0 (12A7209), just like App Store version, but the documentation reader works properly. Sigh!
Wow! Just realized the Core Data diagram view is MIA in Xcode 14. You would think there would be a word about this in the release notes, but NO. NO we disappeared this feature. NO this is a known omission. NOTHING.
Very few style points awarded for this maneuver!
Now that I'm past being upset about the removal of the Core Data Diagram View (without notice in version release notes), I want to add my rationale for restoring this feature.
I am working a Core Data model with 29 entities including several parent/child relationships. It's not a perfect relational database by any means. The diagram view was my GOTO to restrain the complexity I was modeling. If I could not unravel the diagram to keep the lines from crossing, then there likely was something wrong. Now I am looking at my data model in the traditional editor view and I have no idea how these forcibly alphabetized entities relate to each other a s a group. It's a HUGE LOSS for me, and I am VERY DISAPPOINTED.
OK, so I'm only one developer in millions. I'm guessing more will come to realize this is missing as they try to produce a diagram view. But really, Apple, this is a sleazy slight of hand you just foisted on all of us.