3

After getting the error described at the link below, I have set the Transfomer to NSSecureUnarchiveFromData (it was nil before) for an entity's attribute.

CoreData crash error Xcode 11 Beta, IOS 13 Beta

I am using the transformable type to store an array.

Everything seems to work fine when I update my app, and data is preserved, however, I haven't had to perform any kind of migration. I just made the changes in the same xcdatamodel that I had before.

Why haven't I had to do a migration, or should I have done one and could problems be caused further down the line if I don't do one?

user13583757
  • 51
  • 4
  • Did you manage to store any data for that attribute before you got the error, if no then I don't see why a migration would be needed. – Joakim Danielson Jun 01 '20 at 13:35
  • 1
    Yes, as the app is already on the app store. I tested by downloading my app from the App Store, storing some stuff to Core Data, and then running my app from Xcode - the data was retained. – user13583757 Jun 02 '20 at 12:53

1 Answers1

0

Yes, you need to do migration. Here is some more information for this

Core Data: Rename Attribute without having issues with users and their current data

Mitesh
  • 504
  • 2
  • 8