'NSKeyedUnarchiveFromData' should not be used to for un-archiving and will be removed in a future release #358

New Issue

Closed

opened 2025-12-29 15:29:57 +01:00 by adam · 8 comments

adam commented 2025-12-29 15:29:57 +01:00

Owner

Copy Link

Copy Source

Originally created by @sebastien-tribu on GitHub (Feb 16, 2021).

Hi,

I recently herited a project for work which uses CoreStore. On launching the app on Simulator (but same warnings appear on device), the app will load data from using fetchOne, like so:

    func image(with id: String) throws -> Image? { // Image is autogenerated in Image+CoreDataClass.swift
        let image = try CoreStoreDefaults.dataStack.fetchOne(
            From<Image>()
                .where(\.id == id)
        )
        return image
    }

Here's the issue: every time that the data is loaded, a bunch of runtime warnings appear (i.e. one per loaded image in my use case.):

[general] 'NSKeyedUnarchiveFromData' should not be used to for un-archiving and will be removed in a future release
[general] 'NSKeyedUnarchiveFromData' should not be used to for un-archiving and will be removed in a future release
[general] 'NSKeyedUnarchiveFromData' should not be used to for un-archiving and will be removed in a future release
...

1. According to this stackoverflow question, it could be caused by transformable attributes, but I don't even know where to start to debug this using CoreStore. How would you debug this in CoreStore?
2. Do you know in which curcumstances data could be "wrongly" saved in CoreStore causing these un-archiving warnings? (differentiating pre-iOS 14 and iOS-14, perhaps ?)

Thank you !

Originally created by @sebastien-tribu on GitHub (Feb 16, 2021). Hi, I recently herited a project for work which uses CoreStore. On launching the app on Simulator (but same warnings appear on device), the app will load data from using `fetchOne`, like so: ``` func image(with id: String) throws -> Image? { // Image is autogenerated in Image+CoreDataClass.swift let image = try CoreStoreDefaults.dataStack.fetchOne( From<Image>() .where(\.id == id) ) return image } ``` Here's the issue: every time that the data is loaded, a bunch of runtime warnings appear (i.e. one per loaded image in my use case.): ``` [general] 'NSKeyedUnarchiveFromData' should not be used to for un-archiving and will be removed in a future release [general] 'NSKeyedUnarchiveFromData' should not be used to for un-archiving and will be removed in a future release [general] 'NSKeyedUnarchiveFromData' should not be used to for un-archiving and will be removed in a future release ... ``` 1. According to [this stackoverflow question](https://stackoverflow.com/questions/64583182/how-to-determine-which-core-data-transformable-attribute-is-not-using-secure-cod), it could be caused by transformable attributes, but I don't even know where to start to debug this using CoreStore. How would you debug this in CoreStore? 2. Do you know in which curcumstances data could be "wrongly" saved in CoreStore causing these un-archiving warnings? (differentiating pre-iOS 14 and iOS-14, perhaps ?) Thank you !

adam added the question label 2025-12-29 15:29:57 +01:00

adam closed this issue 2025-12-29 15:29:57 +01:00

adam commented 2025-12-29 15:29:58 +01:00

Author

Owner

Copy Link

Copy Source

@JohnEstropia commented on GitHub (Feb 17, 2021):

Hi, thanks for the feedback. The deprecations have been handled in the develop branch, so feel free to use that branch for now. I'm currently finalizing documentations for some new features and I'll push the official update to master when that's wrapped up.

@JohnEstropia commented on GitHub (Feb 17, 2021): Hi, thanks for the feedback. The deprecations have been handled in the `develop` branch, so feel free to use that branch for now. I'm currently finalizing documentations for some new features and I'll push the official update to `master` when that's wrapped up.

adam commented 2025-12-29 15:29:59 +01:00

Author

Owner

Copy Link

Copy Source

@JohnEstropia commented on GitHub (Feb 17, 2021):

I'd ask just in case, but do you have transformable attributes that implement custom transformers? If so then those transformers need to be updated in your side, and possibly to implement the proper migration for those data as well.

@JohnEstropia commented on GitHub (Feb 17, 2021): I'd ask just in case, but do you have transformable attributes that implement custom transformers? If so then those transformers need to be updated in your side, and possibly to implement the proper migration for those data as well.

adam commented 2025-12-29 15:29:59 +01:00

Author

Owner

Copy Link

Copy Source

@sebastien-tribu commented on GitHub (Feb 17, 2021):

Hard to tell right now but I do have a sense that this could be the case. I'll come back here if I can wrap my head around this piece of code. Thanks

@sebastien-tribu commented on GitHub (Feb 17, 2021): Hard to tell right now but I do have a sense that this could be the case. I'll come back here if I can wrap my head around this piece of code. Thanks

adam commented 2025-12-29 15:29:59 +01:00

Author

Owner

Copy Link

Copy Source

@JohnEstropia commented on GitHub (Feb 17, 2021):

If you have a .xcdatamodeld file in your project, you can look for any Transformable attribue and check if their Transformer or Custom Class is set in the model editor. If they are, you can search your project for classes or strings that match those names.

@JohnEstropia commented on GitHub (Feb 17, 2021): If you have a .xcdatamodeld file in your project, you can look for any Transformable attribue and check if their `Transformer` or `Custom Class` is set in the model editor. If they are, you can search your project for classes or strings that match those names.

adam commented 2025-12-29 15:30:00 +01:00

Author

Owner

Copy Link

Copy Source

@sebastien-tribu commented on GitHub (Feb 17, 2021):

Right that's what the StackOverflow question suggested, but there is no .xcdatamodeld file to be found 🤔 still searching

@sebastien-tribu commented on GitHub (Feb 17, 2021): Right that's what the StackOverflow question suggested, but there is no .xcdatamodeld file to be found 🤔 still searching

adam commented 2025-12-29 15:30:01 +01:00

Author

Owner

Copy Link

Copy Source

@JohnEstropia commented on GitHub (Feb 17, 2021):

If you can't find xcdatamodeld files, it's likely your project uses CoreStoreObject subclasses instead. You can search for these and look for either Value.Transformable (classic syntax) or @Field.Coded (new syntax) properties

@JohnEstropia commented on GitHub (Feb 17, 2021): If you can't find xcdatamodeld files, it's likely your project uses `CoreStoreObject` subclasses instead. You can search for these and look for either `Value.Transformable` (classic syntax) or `@Field.Coded` (new syntax) properties

adam commented 2025-12-29 15:30:01 +01:00

Author

Owner

Copy Link

Copy Source

@sebastien-tribu commented on GitHub (Feb 19, 2021):

Aha, I was mistaken, we do have a .xcdatamodel file ! I'll create a new model version to fix these warnings on our project.

Many thanks for your guidance @JohnEstropia

@sebastien-tribu commented on GitHub (Feb 19, 2021): Aha, I was mistaken, we do have a .xcdatamodel file ! I'll create a new model version to fix these warnings on our project. Many thanks for your guidance @JohnEstropia

adam commented 2025-12-29 15:30:01 +01:00

Author

Owner

Copy Link

Copy Source

@JohnEstropia commented on GitHub (Feb 21, 2021):

@sebastien-tribu I see. Just be sure to test your migrations because there is the possibility that the old encoded objects (which were encoded using the deprecated encoder) may not be compatible with the new secured archivers.

Good luck!

@JohnEstropia commented on GitHub (Feb 21, 2021): @sebastien-tribu I see. Just be sure to test your migrations because there is the possibility that the old encoded objects (which were encoded using the deprecated encoder) may not be compatible with the new secured archivers. Good luck!

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

develop

prototype/swift6

master

prototype/concurrency

minIOS13

prototype/containers

transactionSourceTracking

prototype/swiftui

minIOS11

swift5_3

prototype/propertyWrapperFields

prototype/propertyWrappers

prototype/propertyWrapper

Swift5

throwables

prototype/Swift_4_1

prototype/Swift_4_0

prototype/Swift_3_2

prototype/queryBuilders

temp/develop

corestore4_develop

prototype/mainContextToPSC

master_ios_7_to_9

swift_2_3

gh-pages

_corespotlight-test

9.3.0

9.2.0

9.1.0

9.0.0

8.1.0

8.0.1

8.0.0

7.3.1

7.3.0

7.2.0

7.1.0

7.0.4

7.0.3

7.0.2

7.0.1

7.0.0

6.3.2

6.3.1

6.3.0

6.2.1

6.2.0

6.1.0

6.0.0

5.3.1

5.3.0

5.2.0

5.1.1

5.1.0

5.0.0

4.2.4

4.2.3

4.2.2

4.2.1

4.2.0

4.1.4

4.1.3

4.1.1

4.1.0

4.0.5

4.0.4

4.0.3

4.0.2

4.0.1

4.0.0

4.0.0-beta3

4.0.0-beta2

4.0.0-beta

3.1.1

3.1.0

3.0.3

3.0.2

3.0.1

3.0.0

2.1.3

2.1.2

2.1.1

2.1.0

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

2.0.0

1.6.10

1.6.9

1.6.8

1.6.7

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.1

1.2.0

1.0.2

1.0.1

1.0.0

0.2.1

0.2.0

0.1.2

0.1.1

0.1.0

Labels

Clear labels

abandoned

corestore bug

discussion

duplicate

enhancement

fixed

fixed

help wanted

in progress

investigating

ios/compiler bug

irreproducible

looking for workarounds

not a bug

pending

pending docs update

pull-request

Mirrored from GitHub Pull Request

question

regression

user bug

wontfix

No labels question

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

adam (Adam Melkus)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/CoreStore#358