Thank you for the information. I've gone ahead and raised those bugs.
Apple CryptoKit Documentation not marked as supporting visionOS: FB13168808
visionOS Simulator Secure Enclave Unavailable: FB13168845
Magnifico
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
Post
Replies
Boosts
Views
Activity
Hey, thanks for the speedy response.
I tried to run our app on the visionOS 1 beta 3 Simulator Runtime and got a thrown exception noSEP when trying to use ;
let access = SecAccessControlCreateWithFlags(kCFAllocatorDefault,
kSecAttrAccessibleWhenUnlockedThisDeviceOnly,
.privateKeyUsage,
&error)!
CryptoKit.SecureEnclave.P256.KeyAgreement.PrivateKey(accessControl:access)
SecureEnclave.isAvailable reports false for the visionOS simulator but true for the iPad iOS 17 simulator (on an M1 MacBook Pro).
And when I was checking the docs and I didn't see visionOS 1.0+ listed.
Cheers
There's a post about this very issue in the Swift Forums. No resolution, but some further diagnosis.
I'm experiencing the same issue.
I can bypass it with git lfs install --skip-smudge in the host app, but it's not deterministic. Also, even if that works, Xcode will then download the pointer to the lfs file, not the actual file.
This is with Xcode Version 13.2 beta 2 (13C5081f)