Skip to main content

Dealing with Core data migration(lightweight) in an iOS app written in Swift

So a while ago, I wrote on how I discovered the existence of this thing call Core Data migrations, by having my app crash when I added a new entity to my core data model. So the solution to that is actually not very hard, the only issue I had was that a majority of the solutions out there, deal with it in apps built with Objective-C and I needed a solution in Swift. I am not very surprised by this given how new Swift is.

Problem

I have defined the problem in mode detail in one of my previous posts, its a small post and I would suggest having a read of it to better understand the problem. Anyway in a nutshell, I was working on my iOS app which used Core data, so I added an entity to my data model, deployed the app, it was saving and retrieving data and it was all working fine. Then I added another entity to my data model and then the app crashed. So then I was looking for a solution to why my app was crashing and what I can do to fix it.

Solution

Once again in a nutshell the solution involves performing what is called a lightweight migration and this video does a pretty good job of explaining how to add model versions. However it presents the solution in an app built using Objective-C and I was/am building my app using Swift. Now the solution presented in that video is pretty much the same for an app written using Swift, well everything except the last part where we ask our AppDelegate to automatically migrate persistent data stores.

If the Xcode project for the app has been creating using Core Data, you will see the initialisation of persistentStoreCoordinator in the AppDelegate.  In it there will be this line

if coordinator!.addPersistentStoreWithType(NSSQLiteStoreType, configuration: nil, URL: url, options: nil, error: &error)
As evident from the line above, the options being passed into it are nil (null), so we need to pass the following options to it.

var options: NSDictionary = [NSMigratePersistentStoresAutomaticallyOption: true, NSInferMappingModelAutomaticallyOption:true]
The attached screenshot shows, how I accomplished this little Xcode project I made just to get the hang of core data migrations.
Have a look at the variable options of type NSDictionary and how it is used


Comments

Indie Test Developer said…
thanks for sharing wonderful article on Tech Stuffs
23 October 2019 at 21:03
Alfred Avina said…
It requires a well-structured data and the efficient approach to use data migration as a service. The proven solution of the data migration provided by your services helps in performing the successful movement from the old to the required system.
29 October 2019 at 17:29
Post a Comment

Popular posts from this blog

Upload to AWS S3 from Java API

In this post, you will see code samples for how to upload a file to AWS S3 bucket from a Java Spring Boot app. The code you will see here is from one of my open-source repositories on Github, called document-sharing. Problem Let’s say you are building a document sharing app where you allow your users to upload the file to a public cloud solution. Now, let’s say you are building the API for your app with Spring Boot and you are using AWS S3 as your public cloud solution. How would you do that? This blog post contains the code that can help you achieve that. Read more below,  Upload to AWS S3 bucket from Java Spring Boot app - My Day To-Do (mydaytodo.com)
Post a Comment
Read more

Addressing app review rejections for auto-renewing subscription in-app purchase (iOS)

The ability to know what the weather is like while planning your day is a feature of  My Day To-Do  Pro and as of the last update it’s also a part of the  Lite version . Unlike the Pro version it’s an auto-renewing subscription based  in-app purchase (IAP)  in the Lite version. What means is that when a user purchases it, the user only pays for the subscription duration after which the user will be automatically charged for the next period. Adding an  auto-renewing  subscription based IAP proved to be somewhat challenging in terms of the app store review i.e. the app update was rejected by the App Review team thrice because of missing information about the IAP. Therefore in this post I will share my experiences and knowledge of adding auto-renewing IAP in hopes to save someone else the time that I had to spend on this problem. In-App purchase This year I started adding IAPs to My Day To-Do Lite which lead to learning about different types of IAP...
1 comment
Read more

Ionic app with a Django backend: Part 2 - The Ionic app

In this post, I will continue from where we left in Part 1 of this series.  In part 2, I will talk more about the front-end side of things. Ahh, I have a background in web development, hence I call this front-end, but that's not the most accurate thing to say in these modern times. So the right way to say this is, I will talk about the Ionic app in this Github repository(IonicAppWithRestBackend) in more details in this post. So what did we do in part 1? In part 1, we got to the point of running our backend on the web server that ships with Django . To refresh your memory, this is how we got the backend server running, Clone the repo git clone https://github.com/cptdanko/IonicAppWithRestBackend Navigate to the backend project directory cd IonicAppWithRestBackend/backend/python_django/restBackend/ Note: if you are using Windows, you may want to change "/" to "\" in the above command. Once there you can run the backend server with the follow...
Post a Comment
Read more