Since upgrading to Xcode 12 and iOS 14, I have been getting warnings that my Transformable properties in Core Data should be using NSSecureCoding.
However, after adopting NSSecureCoding, I still receive this message. I have implemented NSSecureCoding across the board, and have created a single subclass of NSSecureUnarchiveFromDataTransformer that allows all of these conforming custom data types as top level classes. I register this subclass as a value transformer before constructing my Core Data container. And I have set all the "Transformer" attributes in my managed object model to my custom transformer's name. This has not seemed to make a difference to Core Data, though. I still receive the warnings in my logs. Does anybody else have this problem, or any idea how to resolve?
Code Block CoreData: fault: One or more models in this application are using transformable properties with transformer names that are either unset, or set to NSKeyedUnarchiveFromDataTransformerName. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead. At some point, Core Data will default to using "NSSecureUnarchiveFromData" when nil is specified, and transformable properties containing classes that do not support NSSecureCoding will become unreadable.
However, after adopting NSSecureCoding, I still receive this message. I have implemented NSSecureCoding across the board, and have created a single subclass of NSSecureUnarchiveFromDataTransformer that allows all of these conforming custom data types as top level classes. I register this subclass as a value transformer before constructing my Core Data container. And I have set all the "Transformer" attributes in my managed object model to my custom transformer's name. This has not seemed to make a difference to Core Data, though. I still receive the warnings in my logs. Does anybody else have this problem, or any idea how to resolve?