What are Apple's plan for Transformable Custom class [Double]

Question

Created Jul ’21

Replies 1

Boosts 0

Participants 2

For simplicity when storing arrays of Int, Double, or Date I placed [Int], or [Double], or [Date] in the Attribute custom class field (see screenshot), however when the app compiles the following error is shown:

Misconfigured Property: Entity.timestamp is using a nil or insecure value transformer. Please switch to NSSecureUnarchiveFromDataTransformerName or a custom NSValueTransformer subclass of NSSecureUnarchiveFromDataTransformer

Does this mean that Apple will be dropping this feature, i.e. the option of adding arrays this way will be removed, or if they update their code will the data in my database be unreadable?

What is best practice of storing large data arrays in core data?

Screenshot 2021-07-14 at 18.07.59.png

Boost

Answer 1

DelawareMathGuy OP

Jul ’21

hi,

i think you should take the error message as is and

paste the string NSSecureUnarchiveFromDataTransformerName directly into the Transformer entry where it indicates "Value Transformer name".

that will do it.

as to what this means in the future: who knows? i doubt that it will go away. this has more to do with security rather than any feature that will be changing.

as for best practices: transformable data is not directly searchable in Core Data. that doesn't mean that you cannot search by dates, pulling all records and then, one-by-one, examining its array of dates. it's just that Core Data cannot do it with a simple fetch.

hope that helps,

DMG

0