“nfc”

It is not possible to scan NFC tags silently without the UI. This is by design and there is no way to eliminate all UI elements. While you can Add Support for Background Tag Reading to your app, this will only change the UI shown - a notification instead of the full NFC UI, and the user will need to interact with the notification for your app to be launched.

At this time, CoreNFC functionality is only available on iPhones with NFC capability. We cannot discuss future changes to hardware or software. You can always determine the availability at runtime by checking the NFCReaderSession.readingAvailable property to determine whether the user’s device supports scanning for and detecting NFC tags, and then handle your user experience gracefully depending on the outcome. This way your app would be ready to use any functionality if it were to become available in future OS or device versions.

To be able to interact with payment cards, you will need to enroll in the NFC & SE Platform. You can find the eligibility requirements and the steps to take to enroll at the link. You would use the CredentialSession API instead of the regular ReaderSession APIs in CoreNFC. Starting a CredentialSession will allow yo auto interact with payment cards. Implementing the communication between your app and the card is your responsibility. The protocols of processing the payments will differ from card to card. If you are an authorized developer with a licensing agreement with the credit card supplier, you can get the information on how to implement the protocol directly from them. Implementing the required protocol is domain specific knowledge that we do not support. Once you have implemented the proper protocol, if you have specific questions about the CredentialSession or general CoreNFC APIs, we would gladly assist.

I am not sure what you mean by since NFC cannot be enabled under the separate Apple Developer account Base NFC functionality is not restricted to be used at the account level. So if the app is only using basic NFC functionality, the other account can use their own credentials, profiles, and certificates to build and publish the app. If you are using a special NFC based functionality that requires special permission from Apple, those would be limited to be used only by the account and in some cases, only the app they were assigned to. If the app is required to be released under the other account, they will have to acquire the necessary permissions, create the necessary certificates and profiles and build it themselves to publish it. You cannot build an .ipa with your account and have it published by another account which does not have the necessary permissions.

Thank you! The APIs listed below are utilized to identify FIDO HID devices exclusively, with their corresponding callback registration functions shown here. // Match only FIDO HID devices let matchingDict: [String: Any] = [ kIOHIDDeviceUsagePageKey as String: 0xF1D0 ] IOHIDManagerSetDeviceMatching(mgr, matchingDict as CFDictionary) // Register callbacks IOHIDManagerRegisterDeviceMatchingCallback(mgr, deviceAddedCallback, UnsafeMutableRawPointer(Unmanaged.passUnretained(self).toOpaque())) IOHIDManagerRegisterDeviceRemovalCallback(mgr, deviceRemovedCallback, UnsafeMutableRawPointer(Unmanaged.passUnretained(self).toOpaque())) // Schedule with current run loop IOHIDManagerScheduleWithRunLoop(mgr, CFRunLoopGetCurrent(), CFRunLoopMode.defaultMode.rawValue) let result = IOHIDManagerOpen(mgr, IOOptionBits(kIOHIDOptionsTypeNone)) Randomly it crashes at runloop Terminating Process: SecurityAgentHelper-arm64 [2303] Application Specific Information: abort() called Thread 0:: Dispatch queue: com.apple.main-thread 0 libsys