Re: Secure coding NSArray

2016-02-15 Thread Quincey Morris
On Feb 15, 2016, at 09:44 , Quincey Morris wrote: > >> [archiver encodeObject: model forKey: @"model"]; Oh, in the test project that I pasted this code from, I used “model” as my root object key. In the real project, I’m using NSKeyedArchiveRootObjectKey, which seems like a better choice

Re: Secure coding NSArray

2016-02-15 Thread Quincey Morris
On Feb 15, 2016, at 03:43 , Dave wrote: > > Do you know if same thing applies to dictionaries as well as arrays? In the project that got me started on this, I don’t yet have any dictionaries, so I don’t know. But I would assume so. On Feb 15, 2016, at 04:34 , Michael Starke wrote: > > I am

Re: Secure coding NSArray

2016-02-15 Thread Michael Starke
Hi Quincey, I am unable to reproduce your exception. Is this something related to swift interoperability? In pure objective-c environments it seems to work fine, that is, securely decode without an exception! - Michael > On 15 Feb 2016, at 12:43, Dave wrote: > > Hi Quincey, > > Thank you so

Re: Secure coding NSArray

2016-02-15 Thread Dave
Hi Quincey, Thank you so much for the "heads-up" on this, I will be changing my App to use Secure Coding in the new future and it’s littered with NSArrays and NSDictionary properties. Do you know if same thing applies to dictionaries as well as arrays? All the Best Dave > On 14 Feb 2016, at

Secure coding NSArray

2016-02-14 Thread Quincey Morris
I might be late to this party, but since I just spent hours on it, I’ll document this for anyone who hasn’t run into it yet. If you’re using NSSecureCoding, there’s a problem decoding NSArray objects. You can’t use this: myArray = [coder decodeObjectForKey: @“myArray”]; and you can’t u