core-data-migration

I built an app about a year and a half ago that I'm coming back to. It was the project I cut my Swift teeth on and obviously a lot has changed since then, both in the language and my Swift abilities. Yesterday for the first time, I updated my single CoreData model to add an optional string attribute. I did the file generation bit and made sure in the inspector column the new data model is appropriately selected. On my Simulator and testing devices, I need to delete the old version of the app to install the new version or I get a crash. I assume that's just part of the development environment

I updating my database with a lightweight migration. If I do the update on my device through xcode in debug mode everything runs fine. If I load the app through iTunes as a archive file it will crash before loading the rootViewController. This only happens with my large test database >100mb. I don't get anything useful in the crash log and am not sure what to do with this. His is the only relevant line I can find in the crash log. Unknown thread crashed with unknown flavor: 5, state_count: 1 Normally this would be reflected in the crash report (It would say something about failing to launch in

On my first app I used within my persistant store coordinater a NSXMLStoreType. [storeCooordinator addPersistentStoreWithType:NSXMLStoreType configuration:nil URL:storeURL options:options error:nil]; Now, I like to change to a NSSQLiteStoreType: [storeCooordinator addPersistentStoreWithType:NSSQLiteStoreType configuration:nil URL:storeURL options:options error:nil]; The app crashes, if I simply change the store type. So what I have to do? May I have to do once: check if the old store exists and if yes convert it to sqlite and delete afterwards the old xml store? I have no idea how to convert

My fear is the change of the data model in subsequent releases. I created a new xcdatamodel file in Xcode which is not versioned by default. I know you can click somewhere and make it "the first version". In the Groups and Files tree the xcdatamodel file gets a thick black arrow on the left side which you can click to see all the versions inside. My file does not have that thick arrow so is not versioned. Does this cause big problems later? Is it needed to version it right from the start to make lightweight migration work later? Once the app is shipped to users this can't be changed anymore.

I use Core Data and lightweight migration for my iPhone app. Suppose I have created 3 versions of the data model for the app. One user installed the early version of my app and its data model version is still v1. When the user update the app to the latest version which has the data model version v1,v2 and v3, what happened during the update? The sqlite database migrate from v1 to v2 first and then migrate from v2 to v3? Or it just jump from v1 to v3? Internally, I believe Core Data lightweight migration will apply the changes to each subsequent version in order, but for your purposes you can

You know how you can Reset the coredata store on an iPhone simulator when you've changed your entity structure? Do I need to perform a similar process when I've created a new version of my core data store that is different from what I last ran on my iPhone? If so, how, please? Thanks Just for convenience, until you code a way to remove the persistent store through your app, you can just delete the app off the phone. (Hold your finger on the home screen until icons get wiggly, then click the x on your app.) Then with your phone connected to your Mac, choose Product > Run in XCode and it will

Starting from the standard Xcode Document-based Application w/ CoreData template on 10.7, I'm experiencing some frustrating behavior. I'm sure it's something simple that I'm overlooking. Let's say in my NSPersistentDocument subclass, I have something like this, hooked up to a button in the window: - (IBAction)doStuff:(id)sender { NSEntityDescription* ent = [[self.managedObjectModel entitiesByName] valueForKey: @"MyEntity"]; NSManagedObject* foo = [[[NSManagedObject alloc] initWithEntity: ent insertIntoManagedObjectContext: self.managedObjectContext] autorelease]; [self.managedObjectContext