OS X 钥匙串：32 至 64 位
我最近在 Mac OS X 上将应用程序从 32 位切换到 64 位。我现在遇到的唯一问题是一些用户抱怨他们现有的钥匙串不再保存，并且无法创建新的钥匙串。在这样的切换之后，钥匙串服务是否有任何原因会停止工作？处理钥匙串的实际代码从未改变。
I recently switched my application from 32 bit to 64 bit on Mac OS X. The only problem that I am having now is some users are complaining that their existing keychains are not being saved anymore and they cannot create new ones. Is there any reason the keychain service would stop working after such a switch? The actual code to process the keychains never changed.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果不查看相关代码，很难说清楚，但由于钥匙串 API 是 C 而不是 Objective C，因此您可能会在传递某些 UInt32 时遇到一些问题，这些 UInt32 以前可能是从“unsigned int”或“强制”强制的。 int'。
我会检查您对所有 Sec* 例程的调用，并查找类型强制问题的迹象。
It's hard to tell without looking at the code in question, but since the keychain APIs are C and not Objective C, you may be running into some problems with the passing of some UInt32's that may previously have been coerced from 'unsigned int' or 'int'.
I'd check through your calls to all of the Sec* routines, and look for signs of problems with type coercion.