Re: Guidelines on using NSJSONSerialization
Re: Guidelines on using NSJSONSerialization
- Subject: Re: Guidelines on using NSJSONSerialization
- From: Alex Zavatone <email@hidden>
- Date: Thu, 19 Apr 2012 10:53:49 -0400
Thanks. Might be the annotation coordinate list then.
The MapKit annotation list entries use CLLocationCoordinate2D of CLLocationDegrees for long and lat.
Xcode straight out SIGABRTs when trying to convert the mapView.annotations. Looks like I'll have to convert those location Degrees to NSStrings and try again.
Thanks for showing me those notes from the Serialization Class Reference. The line of code wasn't even returning an error so it was a little hard to figure out what was going on.
On Apr 19, 2012, at 10:33 AM, Fritz Anderson wrote:
> On 19 Apr 2012, at 9:14 AM, Alex Zavatone wrote:
>
>> I'm wondering if there are any hard and fast basic rules on why an NSDictionary or NSArray would not be pass the [NSJSONSerialization isValidJSONObject: jDict]
>> test.
>>
>> According to the docs, isValidJSONObject:, returns a Boolean value that indicates whether a given object can be converted to JSON data, so I assume I'm using this correctly.
>>
>> I'm trying to output my mapKit annotation list to a JSON file and I'm rather surprised that the annotation list (even when added to a dictionary key as an object) fails to pass the test.
>
> Is every item in the tree NSString, NSNumber, NSArray, NSDictionary, or NSNull?
>
> — F
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden