“nfc”

What do you mean by copy card to NFC? Are you trying to make a copy of a card to another card? If so, the sample Creating NFC Tags from Your iPhone if both the original and the writable card are accepting MiFare commands. If what you mean by copy to NFC is whether you can emulate a MiFare card using your app, that is complicated. Currently there are several special programs that will allow apps to emulate cards. You can read about the capabilities and requirements for these use cases in the following documents: NFC & SE Platform for secure contactless transactions HCE-based contactless transactions for apps in the European Economic Area (EEA) Tap to Pay on iPhone which will need you to work with a Payment Service Provider in your region All these programs have strict geographic and eligibility requirements, which you can find out at the above links. If you are not eligible at this time, no other use cases are supported. Argun Tekant /  DTS Engineer / Core Technologies

Hi Could anyone give a confirmation on my comment？ In my case , i would read a nfc tag and launch an clip card on my local device, do you mean there is no way now to test the experience from clip card OPEN button to full app? For that , I must upload and publish my app to App Store within App Clip? Is there any possibility to test this whole experience through testflight ? Great thanks!

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