“nfc”

Hello, thank you for your reply. I have a follow-up question: in my case, the user launches the App Clip via NFC. Does this mean the App Clip is using the Background Assets feature, or is it handled differently? Thank you in advance.

@Engineer ,Thanks for sharing your input. I tested NFC feature in my app, without adding the NDEF entry, and it is working. Do we have any official document from Apple regarding the deprecation of NDEF? Appreciate your help.

First, please check the document NFC & SE Platform for secure contactless transactions for the requirements and regional availability of NFC support with Secure Element. NFCTagReaderSession cannot be used for payment cards. You will need to use alternate CoreNFC APIs, which are only available via special entitlements and agreements. The document above will also explain the requirements for getting access to those APIs. Eventually, you will need to enter into an agreement with Apple and request the NFC & SE Platform Entitlement, if you satisfy the requirements as listed in the document above. If you are not able to use those APIs, PassKit framework will be your only remaining option, if appropriate. If you have already requested the relevant entitlements, if approved, you will receive further guidance on how to proceed with your development.

No, you don't need an HTML page with the app-clip-bundle-id meta tag to fix URL invocation (Notes app or UIApplication.shared.open(url)) for TestFlight App Clips. This meta element is for production web/Safari invocations to trigger the card preview; TestFlight restricts dynamic URL taps/open calls despite green Domain Status and approved swcutil (Site/Fmwk Approval: approved). QR/Local Experience works because it bypasses these limits via explicit developer override. TestFlight Limitations Apple docs confirm TestFlight prioritizes controlled testing: Direct launch from TestFlight app (no card, loads clip). QR/NFC with Local Experience (full card flow). Arbitrary URLs (Notes, other apps) intentionally unsupported to mimic beta safety. Your AASA is perfect appclips entry + /numverify/appclip/* components match, CDN-propagated, swcutil validated. Your Options Method Works for Card+Launch? Setup TestFlight Invocations Partial (testers launch via TF UI) App Store Connect > TestFlight > Build > A

It is not possible to suppress this dialog. It is there to indicate to the user that an NFC transaction is taking place.

I have checked the Console could not really find something there and I have created the sample application just to make contact with my NFC Tag from Texas Instrumentation where the NFC Tagreader session is failing Silently, Thats where our development is blocked and we are unable to progress forward, Is there any way to solve this issue or can we have working session with apple for the same issue ?

Yes, this entitlement is restricted by region, along with other eligibility requirements. These are explained in NFC & SE Platform for secure contactless transactions under the Requirements and availability section. The list of regions which it is available in is also in that section. If this list changes, the updated list will be reflected in this section. Without a special entitlement, apps would be limited to interacting with tags that do not require secure element access. there are no workarounds for such apps based or distributed in regions where special entitlements are not available. There are no supported workarounds of this limitation, if such entitlements are not available for you, whether it is due to a region or other requirements.