You are correct, clean install of macOS 15.1b6 with nothing just a test app and I'm still having this issue.
It seems, I did made a mistake when testing before or triggered one of the workarounds I know :)
Thanks for the update.
Tralala
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
It looks like, that the latest macOS 15.1 beta 6 includes a fix for this issue.
Thanks!
Historically, importing multiple times wasn't an issue until now. I'd love it to do nothing as it was on macOS 14, mostly for user who are not up to date with our app.
With that being said, I don't see a reason why I couldn't search for the digital identity and then skip the import, if such identity exists.
Thanks.
Yep, the description of the bug sounds accurate.
There is one interesting workaround (for anyone else, who is experiencing the same issue):
Import PKCS#12 into the "Login" Keychain by opening .pk12 from Finder
Delete the imported PKCS#12 from the "Login" Keychain
At this point, it's possible to import PKCS#12 into Keychain, that is created in a, let's say, home directory.
Has anyone solved/found workaround for this?
I'm getting exactly the same error message when using SecKeychainCreate() with SecPKCS12Import() on macOS Sequoia 15.0 (24A335)
Meanwhile, on macOS Big Sur 11.0.1 (20B29) and Xcode 12.2 (12B45b) the only option that is available - "Any Mac (Apple Silicon, Intel)". I do not see a way, to disable Apple Silicon.