Reason for setObject to be NSData?

[bjarkehs]

Is there a specific reason why setObject only takes NSData?

[dfed]

NSData is how the keychain stores data (see Apple's documentation of kSecValueData). Moreover, conforming toNSCoding is pretty much a requirement for storing any object outside of CoreData.

We've written setString:forKey: and stringForKey: helper methods that make it easy to store passwords and other string values. Out of curiosity, what kind of values are you storing in the keychain?

[bjarkehs]

That makes perfect sense. Thanks for taking your time to explain it. I'm storing a string and also an array of strings. So it's not really a problem to make it into NSData

[dfed]

Awesome. Closing this out.