JSONModel in Swift issue

Question

I am trying to map the json to model in Swift using JSONModel.

Everything works if model doesn't have properties that are JSONModel subclasses.

So in example this works, and it maps the properties successfully:

class Person: JSONModel {

    var name: NSString?
    var gender: NSString?

}

But if I put JSONModel subclass City, this property is not initialized, and it crashes the app when I try to access the city property later (I can successfully access person.name, and person.gender, but on person.city it crashes without any info):

class Person: JSONModel {

    var name: NSString?
    var gender: NSString?
    var city: City? // City is JSONModel subclass
}

It looks like JSONModel cannot map/parse property if it is a JSONModel subclass. Did anyone experienced this and solved it?

Did you get the solution using JSONModel? Or you switched to different library. — Dilip Lilaramani, Jun 08 '15 at 15:54
Thanks vburojevic for replying. Do you mean like this: @objc class Person: JSONModel { var name: NSString? var gender: NSString? var city: City? } — Dilip Lilaramani, Jun 10 '15 at 16:05
I created my Project in Xcode 8.1, Swift 3.0. I'm trying to use JSONModel but i didn't find any solution. Please let me know if you found any solution. Possible provide source code example. Thanks in advance. — Lokesh Chowdary, Dec 19 '16 at 13:20

score 7 · Answer 1 · answered Jul 06 '15 at 15:35

JSONModel does not work in Swift, that's why you're having issues. From the JSONModel readme:

NB: Swift works in a different way under the hood than Objective-C. Therefore I can't find a way to re-create JSONModel in Swift. JSONModel in Objective-C works in Swift apps through CocoaPods or as an imported Objective-C library.

You might be able to get it working in certain edge cases - but the only reliable way to use it, is by writing Objective C code against it, and using these Objective C classes. If you'd like to do pure Swift, you should look at other libraries such as Argo and a bunch of others.

Fawkes · Answer 2 · 2016-02-10T20:35:08.290

Actually the problem with JSONModel in Swift is as follows:

It uses Objc-runtime for understanding what type is each property and as soon as you declare a type which Obj-c runtime does not know how to map, then JSONModel can only map it as a String .........or NSNumber if you know that you have a numeric field.

The way it works: So basically if you declare all the properties that remain nil in your case as Strings, you'll start seeing values. The same works if you declare numeric fields as NSNumber. Both String and NSNumber can be also declared as optionals with no specific problem for JSONModel.

But dare you not to use the primitive types from Swift with optional declaration (Int?, Double?, Bool?). This will not work.

What will work is avoiding by any means declaring as optionals by:

1) var tmpInt : Int = 0, giving a default value

2) var tmpInt : Int!, forcing

Of course these last "workarounds" are totally against why Swift appeared in this world, but this is how you bring the old Objective-C habits in the new modern Swift (;

score 0 · Answer 3 · answered Sep 05 '14 at 08:11

maybe it might help to set the access level to "public" ?

public class Person: JSONModel {
    public var name: NSString?
    public var gender: NSString?
    public var city: City? // City is JSONModel subclass
}

public class City: JSONModel {
    public var name: NSString?
}

JSONModel in Swift issue

3 Answers3