Core Data Migration custom migration

Question

I'm trying to do a custom migration, following the instructions found here, changing an attribute name and type but it doesn't seem to be running the mapping.

Old model has an attribute names "roundDrill" which is a Boolean. The new model has this removed and a new attribute called "drillType" which is a String.

I have a mapping model called "V2V3.xcmappingmodel" where the entity has a custom policy set "Diamond_Painting_Logbok.V2V3". The new attribute has a value of "FUNCTION($entityPolicy, "roundToType:" , $source.roundDrill)"

In the "V2V3.swift" I have the below code

import UIKit
import CoreData

class V2V3: NSEntityMigrationPolicy {
    func roundToType(isRound:NSNumber) -> String {
        NSLog("Round: \(isRound)")
        if isRound.boolValue {
            return "Round"
        } else {
            return "Square"
        }
    }
}

When I print out the value of drillType, I'm getting nil. The NSLog on the function isn't being printed at all. If I change the custom policy name, its not giving me an error so appears as though its being ignored completely

Your custom policy implementation would be ignored if you missed Step 5 in the instructions by Tom Harrington which you linked to. Or maybe you entered your Custom Policy Class Name into the Attributes Inspector of the wrong entity. Please check these. — Jerry Krinock, Apr 06 '19 at 20:36
Have you tried adding the `@objc` mark as in the answer by noobular in the instructions you linked to? It is not in the code you posted. — Jerry Krinock, Apr 06 '19 at 23:31
I’ve tried with and without, no difference. Even if I deliberately make a typo in the method name, no error is thrown — Ceri Turner, Apr 06 '19 at 23:54

score 0 · Accepted Answer · answered Apr 09 '19 at 17:36

So I've found the reason for the issue after speaking to apple, its because I don't have a V1 to V2 model, just V2 to V3. Without that, all mapping models are ignored,

They've also said the mapping isn't running correctly as it crashes with "unrecognized selector sent to instance" even though ititss correct, that its a bug.

They've advised to use createDestinationInstances as a workaround so need to figure that out

Core Data Migration custom migration

1 Answers1