|
|
|
|
|
by mpetrov
4629 days ago
|
|
I agree, the whole point of the logout bug is that the keychain is locked, and that happens for a reason. I came up with a different solution that worked great for us: Just pause the startup process of the app (in a non-blocking way) if accessing the keychain fails at startup. Then during applicationDidBecomeActive the startup continues with access to the keychain data. That way we don't weaken the security of our customers. |
|
It's a trade-off between user experience and security. As soon as Apple fixes the reboot issue, we'll increase the security level back to kSecAttrAccessibleAfterFirstUnlock.