Have you considered adding a Swift extension to a PFObject that uses the NSSecureCoding protocol?
I have not tried this action, but it seems reasonable to expect this to work with an error message.
Recommended Action
To comply with NSSecureCoding:
An object that does not override initWithCoder: can match NSSecureCoding without any changes (provided that it is a subclass of another class that matches).
An object that overrides initWithCoder: must decode any private objects using the decodeObjectOfClass: forKey: method. For instance:
SWIFT
let obj = decoder.decodeObjectOfClass(MyClass.self, forKey: "myKey")
In addition, the class must override the supportSecureCoding method to return true.
When using Objective-C, a category seems to be a suitable solution.
source share