“nfc”

[quote='885705022, Frankois944, /thread/729371?answerId=885705022#885705022, /profile/Frankois944'] is it possible to force the UIRequiredDeviceCapabilities? [/quote] I believe that App Review has a way to allow this. However, before you reach out to them you should carefully think about this choice. By narrowing the set of supported devices, you’re prevent existing users of your app from updating to your latest version. You should carefully consider whether that’s worth it, especially when dealing with a very old app. It might be better to simply ship a new app. Or do what endecotp’s recommended above, that is, not make NFC a requirement. Or you could do both, that is, publish a new app that requires NFC and also update your old app such that the existing functionality, the stuff that you’re users have been using for years, continues to work on devices with NFC. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hello, We're reviving of a very old app, we need to use the same app-id. The new one requires NFC and, so, it can now only run on iPhone. is it possible to force the UIRequiredDeviceCapabilities ?

TestFlight distribution and testers have the same requirements as your end users who would be downloading your app from the App Store. This means the testers will have to be: physically be in the EEA logged on to their phones with an iCloud account based in the EEA As explained in the documentation HCE-based contactless NFC transactions for apps in the European Economic Area (EEA), if you have testers outside the EEA, you cannot use TestFlight builds. Testing requirements Apple has developed a solution which allows HCE Developers to develop and test HCE Payment Apps outside the EEA. The new solution allows development and testing on a device through known and well-used means such as Xcode and provisioning of profiles used for testing on devices within a developer’s organization. Developers will be able to have up to 100 test devices outside the EEA. To test HCE-based contactless transactions, you’ll need to test with an iPhone and NFC hardware. CardSession requires the presence of an NFC

I’m not entirely sure who allocates AID values, but some rummaging around on the ’net confirms that AID A000000308000010000100 is definitely associated with PIV. As to your current issue, the doc comments in for the -[TKSmartCardSlotManager createNFCSlotWithMessage:completion:] method says: Warning Caller requires com.apple.developer.nfc.readersession.iso7816.select-identifiers Info.plist record which specifies application identifiers of the NFC cards link which suggests that your solution is the right one. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Dear Team, We request your urgent support to proceed with uploading our application to the Apple App Store. Currently, several of our customers are awaiting NFC credentials provisioning via Apple Wallet, and the delay due too thi issues and is directly impacting their onboarding and usage. This situation is significantly affecting our business operations and customer experience. We kindly ask you to prioritize this request(102864920121.) and let us know if any additional information, changes, or compliance items are required from our side to expedite the process. Your prompt assistance will be greatly appreciated, as many customers are actively waiting for access. Thank you for your support.

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.