Open delfuego opened 1 month ago
One other related/unrelated note: on this (and two other test MBPs in our fleet), the macOS 14.5 upgrade also broke Apple Pay. And our debugging of that led us to all sorts of console log messages related to Secure Enclave weirdness — attempts to access the Apple Pay Secure Enclave container that weren't succeeding, things like that. So we already had a working theory that the macOS 14.5 upgrade brought changes to the Secure Enclave that weren't called out in the release notes… and this just makes that working theory even stronger.
@delfuego good news is this is very unlikely to be an actual data loss – if you haven't restarted yet, try that. We've had a few reports of the SEP getting into a weird state like that occasionally.
Holy crap, that worked, @maxgoedjen! (It doesn't work for the Apple Pay issues, though, which is why I didn't think to try it first.)
I have a git push key and an SSH signing key. I had an issue after updating to 14.5 where /Users/aaronmeurer/Library/Containers/com.maxgoedjen.Secretive.SecretAgent/Data/PublicKeys/
was empty and git couldn't find the ssh signing key (even though both keys appeared in the Secretive GUI). But then, after doing a push operation, my push and SSH signing key magically reappeared and everything worked again.
I could just be misremembering how things were, but it really feels like Secretive is slower after the Sonoma 14.5 update. A no-op git pull
takes 5 seconds and git commit --allow-empty -m "test"
with SSH signing enabled takes 3.5 seconds (git commit --allow-empty -m "test" --no-gpg-sign
takes 0.08 seconds).
Even if it was actually always like this, if anything could be done to improve the performance that would be great.
Sounds like there's enough people hitting that to merit investigation. I'll track that separately in #552.
I updated my MacBook Pro to macOS 14.5, and now, I seem to have (a) lost all my existing SSH keys in Secretive, and (b) get an immediate Secretive crash when trying to create new ones. I'm running Secretive 2.4.1, and have been since January-ish.
When I launch Secretive, I see "No Secrets" under the "Secure Enclave" listing in the sidebar, despite having at least 2-3 keys that I've been regularly using prior to the 14.5 update.
And when I click the + icon to create a new key, I am asked which type (authenticate or notify) and for a name, and then clicking the "Create" button causes an immediate, 100%-reproducible crash of the Secretive app. If I choose "Report" to the crash notice, below is the information it shows me. Please let me know if anything else could be of use to help track down what might have happened!