nfc

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

we have this in config : entitlements: { com.apple.developer.in-app-payments: [ merchant.net.tag ], com.apple.developer.nfc.readersession.formats: [], // Empty array - Expo will use NFC capability from Apple Developer Portal aps-environment: production }, and but we still have this error when we submit app to TestFlight [logs] [Application Loader Error Output]: Validation failed Invalid entitlement for core nfc framework. The sdk version '18.5' and min OS version '17.0' are not compatible for the entitlement 'com.apple.developer.nfc.readersession.formats' because 'NDEF is disallowed'. (ID: 377c83da-9fcc-4903-8c6e-c041d3eedb73) (409)

We are also facing similar issue randomly on our app with required pass suppression entitlement in place, particularly after installing an app update - the Wallet popup unexpectedly appears on tapping NFC reader even when the app is in the foreground. After some time, it starts working correctly again (i.e., the Wallet no longer appears)

We cannot discuss why CoreNFC is not available from app extensions. It just isn't. We cannot discuss future plans either. If this is important for your use case, we always welcome feature requests via the Feedback Assistant There are no ticks, workaround, or entitlements to make CoreNFC work from an extension. Nor it is possible to launch the main app form an extension. Your option 3 of the main app performing the NFC functions and then sharing the data with the extension is about the only way this would seem to work for your use case if I understand it correctly.

You should start by checking the error returned when your reader session is invalidated. You say all setup is done, assuming correctly, but that's where mistakes are most commonly made, by not including the correct entitlements, and declaring the AIDs you need to use with the passport. Also, reading passports is not going to be as simple as reading a regular NFC tag by just tapping. They will usually be protected by an access protocol. You will need to determine the protocol used by the passport you are trying to scan. Older passports use BAC (Basic Access Control), where newer ones may be using PACE (Password Authenticated Connection Establishment). In your app, you need to have implemented the correct protocol both in code and in user flow.

Is tap to pay still needed? i don't want to read passes from wallet nor accept payments. I want to use nfc card reader on the credit card from the bank i work for in the bank of the app i work for to validate the card and activate it. I don't see how it would be related to tap to pay or wallet. we already have apple pay setup but we still get an error about the entitlements missing. So i'm wondering which one i need and if i need to do a specific request to have them knowing we are a bank and already have com.apple.developer.payment-pass-provisioning

This seems to be related to iOS26, app clips also no longer work over NFC

We have the same issue with NFC: app clips stopped working on iOS 26, stating App Clip unavailable

Here's another interesting thing that's happening. I've tried clearing experience cache (Settings -> Developer -> App Clips Testing -> Clear Experience Cache) and immediately after that scanning URLs that don't have app clips as invocation URLs. What sometimes (3 out of 10 attempts) started happening is this: Clear cache Scan NFC tag Shows Open in Safari notification // Expected behavior Scan NFC tag again Shows No app clip available Scan NFC tag again and again and again Shows CPSError Domain error 2 All other attempts it just shows CPSErrorDomain.

Another interesting thing is when reading an NFC card that has just domain without path, it works as expected: https://short.com -- Shows Open in Safari notification, expected behavior since there's no App Clip with this invocation URL. https://short.com/ -- Shows Open in Safari notification, expected behavior since there's no App Clip with this invocation URL. https://short.com/a -- Shows the CPSErrorDomain error 2 popup. There's no App Clip Invocations registered with this URL. When checking these three URLs at Settings -> Developer -> App Clips Testing -> Diagnostics -- it shows the same information for all three URLs (it just shows the same as in the second Diagnostics screenshot I attached in replies above). *Just a reminder that short.com is just an example domain here.