“nfc”

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.

You can check out https://developer.apple.com/documentation/corenfc/building-an-nfc-tag-reader-app for an example of how the entitlements and Info.plist entries are constructed. I can't help you with getting the AID of the NFC device. You may need to contact the manufacturer, if the AIDs are not standard, or documented. Approval depends on what you are trying to do. In order to just read from the tag, or write to the tag, you don't need any approval. If you are trying to emulate a tag (the NFC hardware you are using is a reader), or if the AIDs you are using are of restricted nature (like payment intent, identification, etc.) then you need approval and depending on the region you are operating in, that may or may not be possible, and will require an extensive application process.

My app requires the user to scan an NFC tag for authentication.I provide links with login information on a website with a registered custom URL Scheme.My app should open, let the user scan their NFC tag and send the user back to the previous opened app.Not possible to make it automatic without making the user click the Back to Xxx button?

The same thing happens when you scan an NFC tag containing the URL. At least me and someone else have this issue: https://stackoverflow.com/questions/65150897/swiftui-universal-links-not-working-for-nfc Their work-around is to use a custom URL scheme, but since that's frowned upon these days it would be nice if this was fixed. I assume it's an issue in SwiftUI (or maybe something lower level - I haven't written a UIKit test app to narrow down where the URL ges lost). I did make a quick test to see if custom schemes work, but I could only get it to work when scanning a QR code - not when scanning an NFC tag.

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

attempting to switch to NFCTagReaderSession to communicate at the ISO-DEP / APDU level fails silently. The tagReaderSession(_:didDetect:) delegate is never called, even though the same physical tag is clearly present and readable via the NDEF session. From my observation, it appears that on iOS, once a tag is handled as an NDEF Type 4 tag, Core NFC does not reliably expose it again through NFCTagReaderSession for raw ISO-DEP / APDU communication—especially for NFC-B tags. The session starts successfully but does not surface the tag for APDU exchange. This raises an important question: Is there any supported way on iOS to reliably issue custom APDU commands to ISO 14443-4 (NFC-B) tags like the TI RF430, or is APDU access effectively restricted/filtered by Core NFC when the tag is NDEF-formatted? If this is a platform limitation, it would be helpful to have clarity on whether iOS intentionally blocks APDU-level access for such tags.

Likewise, reading tags was ok but now we see this error opening a ISO1443 Nfc tag

Hi Chandra, wondering if your able to process without notification appears after reading NFC tag.

Hi KhaosT,do you have more information about the nfc-field that is added with iOS9?Thanks,David

Any news on this? Has anybody successfully taken a travel card and made it work with a static nfc code?

I would love to have access to NFC tag functionality for the Apple Watch. There are so many useful functions this would facilitate.

I want to thank you all for a great answer. Great to have a 999 $ phone that can’t write to nfc