“nfc”

Thank you. Your understanding is correct, and I now understand that I cannot write a URL to another smartphone from my iPhone. After purchasing an NFC tag and writing to it, I successfully managed to write the data. Thank you very much for your clear and understandable explanation. I appreciate it.

If I understand your use case correctly, with your Write function you are trying to have your app become an NDEF tag. In other words you are trying to emulate an NDEF tag. Unfortunately, this is not possible. As the name suggests a readerSession is just that. It can read NFC tags. I believe you may have misunderstood the use case for writing to an NDEF tag. While it is possible to use the writeNDEF(_:completionHandler:) to write to an NDEF tag, that is all this function can do - write a payload to an existing NDEF tag. This function does not turn your app into an NDEF tag. What you are trying to do is called Host Card Emulation, and this is only available for apps that fit specific requirements. You can read the rules and requirements at HCE-based contactless transactions for apps in the European Economic Area (EEA) and follow the steps in the documentation to apply if, and only if your conditions and use case matches the stated requirements. Argun Tekant /  DTS Engineer / Core Technologies

Thank you for your support. I update my app as below according to your advice. But the issue not fixed. iPad is still Incompatible Hardware. In project Build Phased, Link Binary With Libraries” section, CoreNFC.framework is Optional. Use NFC feature only if UIDevice.current.userInterfaceIdiom == .phone in program. import CoreNFC always exist. I upload the build to TestFlight but still I can't install it to iPad. TeestFlight app on iPad show Incompatible Hardware. Build Metadata in Test flight section on App Store Connect site show at Device Requirements Device Family: iPhone, iPad Required Capabilities: arm64, nfc The initial version of this app already App Review approved and released on App Store. does it affect update and can't change Compatible Hardware? Best regards, ziotreks

Does the issue still occur? If yes, run Diagnostics in the App Clips Testing on a device as described in Verify the configuration of your released App Clip. Additionally, confirm that you followed the instructions from Choosing the right functionality for your App Clip: To ensure a fast launch experience, App Clips must be small: If you make your App Clip available on devices running iOS 15 and earlier, the uncompressed App Clip binary can be up to 10 MB in size. If you make your App Clip available on devices running iOS 16 and later, the uncompressed App Clip binary can be up to 15 MB in size. If you make your App Clip available on devices running iOS 17 and later, the uncompressed App Clip binary can be up to 50 MB in size if it meets the following conditions: The App Clip only supports digital invocations — for example, from your website or Spotlight search — and not from physical invocations like App Clip Codes, QR codes, or NFC tags People use your App Clip in situations where a reliable interne

It is possible to have a single binary that installs on both. If you want the app to also run on devices with no NFC, the solution is to use weak linking, so the system does not attempt to load the NFC framework/libraries. What you need to do is weak link the CoreNFC framework manually in project settings, and then avoid using it if the app is not running on a supported device (check for iPad). To do this, you need to do the following: in your project Build Phases, the Link Binary With Libraries” section, add the CoreNFC.framework, and then mark it as Optional. This will prevent the app from crashing at launch. the next thing you need to handle is to avoid problematic behavior at App Review or in case a user installs the app on an iPad. For that, you could do a check of the UIDevice.current.model value and not engage any features of your app that would require the use of CoreNFC features. Keep in mind, that App Review will require the app to have some adequate functionality, while not using

Unfortunately this is a very open ended question which is difficult to answer here without understanding what it is you are trying to accomplish. There are many factors and policy differences based on what you are implementing, for what purpose, and in what locations. In any case, to implement NFC payment functionalities, you will need specific entitlements from Apple. When applying for them, you will be able to explain in detail your product plan and any details, and if you are approved, at that point any policies with regards to your implementation will become clear.

I am developing an app and having trouble implementing NFC HCE functionality on iOS. From what I found, NFC HCE seems possible in the EEA, but I need help doing it in other countries. Is there any way to achieve this through a specific license or certification from Apple? Any guidance or references would be greatly appreciated.