[quote='869055022, Yvan.d, /thread/809534?answerId=869055022#869055022, /profile/Yvan.d'] could this type of Keychain item design … lead to the kind of attribute inconsistency [/quote] It’s certainly possible. My experience is that there’s a lot of really bad keychain code out there )-: That’s partly because the SecItem API is way more subtle than people think, and partly because Apple’s initial documentation and sample code for it was… well… less than ideal. Moreover, the keychain is a persistent database where it’s important to not lose user state. So if your app has been around for a while, debugging a keychain problem means that you have to understand your current code and all the previous iterations of that code. There’s a few ways to tackle a problem like this: You could use source control to resurrect old versions of your keychain code, put all that code in a test app, and then try it out. You could use telemetry to understand the state of your users’ keychain items in practice. You could do what you’r
Topic:
Privacy & Security
SubTopic:
General
Tags: