SwiftData error: NSKeyedUnarchiveFromData' should not be used to for un-archiving and will be removed in a future release

Question

Created Aug ’23

Replies 5

Boosts 2

Views 2.2k

Participants 5

I am using SwiftData for my model. Until Xcode 15 beta 4 I did not have issues. Since beta 5 I am receiving the following red warning multiple times: 'NSKeyedUnarchiveFromData' should not be used to for un-archiving and will be removed in a future release This seems to be a CoreData warning. However, I am not using CoreData directly. I have no way to change the config of CoreData as used by SwiftData. My model just uses UUID, Int, String, Double, some of them as optionals or Arrays. I only use one attribute (.unique).

Boost

Answer 1

ACB OP

Aug ’23

I also have this issue. I'm hoping it's a bug that the SwiftData team is planning to fix before release. If not, hopefully Apple releases some guidance for how to resolve this error. In the meantime, I'm ignoring it and hoping for the best.

0

Answer 2

Michael12345 OP

Aug ’23

Apparently this has been fixed in Xcode 15 beta 7

0

Answer 3

tundsdev OP

Sep ’23

This is still an issue for me in Xcode 15 RC.

Below is an example of the transformer I'm using for saving a UIColor

final class ColorValueTransformer: NSSecureUnarchiveFromDataTransformer {

    static let name = NSValueTransformerName(rawValue: String(describing: ColorValueTransformer.self))

    override static var allowedTopLevelClasses: [AnyClass] {
        return [UIColor.self]
    }

    public static func register() {
        let transformer = ColorValueTransformer()
        ValueTransformer.setValueTransformer(transformer, forName: name)
    }
}

0

Answer 4

phspman OP

Jan ’24

Same issue with my transformable array of strings in Xcode 15.2 and iOS 17.3. I'm switching from CoreData to SwiftData and using NSSecureUnarchiveFromData. But still get this error and then the app crashes due to memory. Frustrating I can't move to SwiftData after all of the work I put into changing my code. Good thing I saved a copy of the CoreData version.

https://developer.apple.com/forums/thread/744688

0

Answer 5

JetForMe OP

Aug ’24

I still get this in Xcode 16b5 on macOS in my SwiftData/SwiftUI app. I don't explicitly use NSKeyedArchiver anywhere, nor do I have any transformations on my model objects.

2