“nfc”

Is there an additional propagation or approval step required after the status becomes Received for Advanced App Clip Experiences? From TN3168: Making your App Clip available in the App Store > Retry your invocation later: In rare cases, your App Clip may become unavailable due to factors outside of your control. After Apple approves your App Clip, it may unexpectedly take some time for your App Clip to be available in all the countries or regions you select in App Store Connect. The same situation may occur when you edit your App Clip information in App Store Connect. Retry your invocation at a later time. Additionally, what is the size of your App Clip? Please confirm that you followed the instructions from Choosing the right functionality for your App Clip > Keep your App Clip within size limitations: To ensure a fast launch experience, App Clips must be small. Aim to keep your App Clip binary well below the applicable limit: iOS version Maximum size of the uncompressed App Clip binary iOS 15 and earl

Hi @HAnastasovski, In iOS 18.2 and later, HCE Developers can develop and test HCE Payment Apps outside the EEA. Developers will be able to have up to 100 test devices outside the EEA. Please see the 'Testing requirements section of the following page: HCE-based contactless NFC transactions for apps in the European Economic Area (EEA) https://developer.apple.com/support/hce-transactions-in-apps/ Cheers, Paris X Pinkney |  WWDR | DTS Engineer

Thanks for that info. Based on that, I created a small test project to exercise my normalisation theory: Using Xcode 26.3 on macOS 26.2, I created a new project. I added LSSupportsOpeningDocumentsInPlace and UIFileSharingEnabled to its Info.plist [1]. I wired up a button to my test code, which I’ve pasted in at the end of this reply. I ran the app on an iOS 26.2 device. I tapped my test button. It was able to create the files. I switched to the Files app. And navigated to On My iPhone > My App Name. I tapped test, then test dec (naïve), then test pre (naïve). The first two worked; the last one failed as you described. The difference between these file names is that the test dec (naïve) uses a decomposed ï (NFD) whereas test pre (naïve) uses a precomposed one (NFC). Clearly, that’s causing problems for Quick Look in the Files app and elsewhere. So, there are two things for you to do here: Please file a bug against iOS about this. It should be able to handle both normal forms equivalently. Once you’

It is not possible to predict the cooldown time, as it is literally necessary for the NFC subsystem to cool down from a thermally increased state. The time required might be different not only from one phone to another (depending on what kind of case they are in, whether they are in a warm or cool environment, etc.) but even on the same phone from situation to situation based on how heavily and frequently the NFC has been used recently and in what thermal state that usage has put the system in. The best solution to implement for an app at this time, is to no promise a set time zone but to use generic language that the device needs some time. Perhaps based on the bug report the team may decide to implement a callback to the app when the conditions are restored. But until then, waiting and retrying is the remaining option.

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