I'm passing in kSecAttrAccessibleWhenUnlockedThisDeviceOnly. But I've thought that could be the cause* and also tried kSecAttrAccessibleWhenUnlocked, kSecAttrAccessibleAfterFirstUnlock and even kSecAttrAccessibleAlways. The issue exists no matter what the protection is.
*since all the Macs that exhibit the issue are on 10.12 but also don't have a Secure Enclave (Intel Macs without T1 or T2 chip).
I've also just filed FB12189765. There's a sample project attached to the feedback. I can't seem to attach a zip here but I'm attaching the relevant code as a .txt for reference here.
ContentView.txt
paulo_andrade
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
Did you ever find a solution for this?
Found the solution, add:
-Xcc -fmodule-map-file=$(GENERATED_MODULEMAP_DIR)/<YourSwiftModuleImportedFromObjC>.modulemap
To Other Swift Flags.
Just ran into this (Swift module used in Objective-c Framework then used in Swift). Did you ever find a solution?
This has been my experience as well. Hopefully this is something Apple can improve upon.
Have you got any reply for this yet? I've filed a Feedback, contacted App Store Connect support and burned a DTS but to no avail. I've yet to receive any reply.
This has been fixed in the latest Xcode-beta.
Were you able to solve this somehow? We're currently having the same issue.