nfc

You may not be able to force reproduce these errors easily, so you may need to mock the error conditions to test your code paths. radiodisabled - the NFC radio can be disabled on a managed device via an MDM profile. That is when you will get this error transmissionerror - this would be caused by problems during transmission between the two NFC devices. Could be noise, could be interruption. This is a non-terminal error, meaning you can try the send operation again, as long as the connection is still active emulationStopped - you would get this error if you try to send a command after calling stopEmulation() accessnotaccepted - means the user declined the permission systemeligibilityfailed - is when the app is running on a device that is not eligible to use CardSession. Either not correctly configured, or outside the eligibility regions. Argun Tekant /  DTS Engineer / Core Technologies .

@kocaatli in old versions of iOS it was possible to negotiate a session with an Apple Wallet pass if it was manually selected: https://youtu.be/FKwzPYBX4aY @swakitaki it is possible to read transit cards without authentication. It depends on the issuer's implementation but here's an example: https://github.com/kormax/apple-device-as-access-card The NFC @ SE Platform entitlement is for creating a credential that would be served by an application different from Apple Wallet, as I understand it. If you want to offer an iOS app for train conductors to scan people's transit cards and managing the issuance of these cards, your best bet is to use an external reader like so: https://youtube.com/shorts/csC_rloFr90

The current iOS implementation of HCE interoperability (EEA only), with regard to ISO 7816-4 protocol communication, presents significant challenges. When using the CardSession functionality to interact with NFC readers, an application can be configured to listen for a SELECT command using an Application Identifier (AID) as specified by ISO 7816-5. However, the SELECT command is not always honored by the system. Currently, users are required to either switch between default contactless apps to allow the SELECT command to reach the intended application or manually open the app and initiate a presentmentIntent. While the presentmentIntent itself is not a workaround, its use for directing NFC commands in this manner is. This approach prevents the default contactless app from interfering and ensures that the user’s app is selected. However, this is not consistent with the ISO 7816 standard, which specifies that an application must be directly selectable by its AID, if its AID is known. This is a

Follow up question to this. I am trying to do something similar -- create an iOS app that train conductors will use, and they would need to scan people's transit cards in the app to check how much credit they have left on their transit card. Most people have set their transit cards on express mode (no need for biometric authentication). My question is, using the NFC & SE Platform entitlement, can developers read transit cards without it requiring user authentication? Or does the user need to unlock their phone before scanning, even if it is set to express mode?

It is technically possible. But like you surmised it is restricted due to Secure Element isolation. Basic CoreNFC APIs do not support identity or payment related AIDs. But there is a new NFC & SE Platform for secure contactless transactions Information here: NFC & SE Platform for secure contactless transactions Before investing time and resources, first you should examine the Requirements and availability section to make sure these are available for use in your or your client's region, and your use case and company specifics are suitable. If it is, then you can follow the instructions at that document to apply for access to the API. Any information not clarified/present at this link will be provided once you request access and sign a confidentiality agreement. Details are in the Requesting access to the NFC & SE Platform section. Technically, you will be using the CredentialSession APIs We cannot answer whether this API would be suitable for your specific use case. You w

In the Diagnostics section of the Settings app, the NFC domain shows a warning: “The URL does not match the associated domains for this App Clip.” However, I have verified that my AASA configuration is correct, and the cached AASA file on https://app-site-association.cdn-apple.com/ is also correct.

As of Safari 18.3 (macOS, iOS, iPadOS), authenticatorAttachment still set to platform instead of cross-platform when registering a credential using a security key (usb/nfc transport) or mobile phone (hybrid transport).