[quote='822120021, AntonPastrevich, /thread/822120, /profile/AntonPastrevich'] We've filed FB22448572 for this [/quote] Thanks. That’s the best path forward for this. [quote='822120021, AntonPastrevich, /thread/822120, /profile/AntonPastrevich'] Is there a known issue with securityd’s keychain authentication after 26.4? [/quote] Well there is now that you’ve filed a bug about it (-: Seriously though, as I mentioned on that other thread you found, macOS 26.4 has significant changes to how we unlock the login keychain. In that thread, the developer is doing something unusual, and it’s not clear what the right path forward is. But in your case my understanding is that you’re doing something pedestrian — accessing a keychain item from early in your app’s lifecycle — and that makes the path forward clear: File a bug so that the keychain team can investigate. Which is what you’ve done (-: [quote='822120021, AntonPastrevich, /thread/822120, /profile/AntonPastrevich'] Would migrating to the data protection keychain …