“nfc”

Dear Apple Support Team, I am writing to bring to your attention an issue we have encountered with NFC (Near Field Communication) functionality on Apple devices, specifically related to the initiation of new NFC sessions after tapping the 'Cancel' button during a previous session. This issue seems to occur predominantly when the device is in Aeroplane mode. The problem we are facing is that the NFC pop-up fails to initiate when a user tries to start a new NFC session after cancelling a previous one. This limitation has caused inconvenience for both our team and our users, as we rely heavily on NFC technology for various applications. We kindly request your support and expertise in investigating and resolving this issue. We understand the complexities involved in addressing such matters and greatly appreciate your dedication to improving the functionality of Apple products. By addressing this problem, you would contribute to enhancing the reliability and user experi

I am developing an access controller RF (NFC). I know that the ADP developer account can only handle NFC Tags. Can I use NFC AID and HCE in ADEP? ADEP supports hotel card keys, employee badges, etc. Is it NFC? Or is it NFC+BLE?

Recently Apple updated Xcode and had one change for App Clips. For a URL to launch it needs the additional of nullable See link here. - https://developer.apple.com/documentation/app_clips/apactivationpayload/3580308-url?changes=latest_major&language=objc One problem. My App Clip works fine but there is nowhere in the code where to use the code defined in the link, either the previous or the new updated code. I only use NFC for the App Clip. So does this not involve NFC? It mentions payload which I'm used to hearing about with NFC chips, so that's why I'm wondering about it. I've also noticed NFC reading less consistently as background reader. Please let me know if this line has anything to do with NFC, and why my app would still work even though I don't even use this line anywhere in my code. Thank you truly and any help is appreciated. I just don't want to be missing something that might break my app in an upcoming update.

I have a question about suppressing Apple Pay when a particular app is open. The app concerned displays a QR code which is read by a reader. Unfortunately, the reader is within the vicinity of a fixed NFC reader and is causing Apple Pay to open, stopping the QR code from being read. I’m aware that one option is to place the QR code within Apple’s Wallet where the NFC reader can be disabled, however I’ve also been told that it’s possible to resolve this without needing to pass the QR code through to the Wallet. Any suggestions welcome (moving the reader isn’t currently an option!). Thanks.

We are developing an iOS application that requires NFC-based communication using ISO 7816 / ISO 14443 standards for secure element interaction as part of a card provisioning workflow. We would like clarification on the following points: Is it possible to provision a payment card or securely add a card to an NFC-enabled device using direct ISO 7816 APDU communication via NFCTagReaderSession? If not, is Apple Pay In-App Provisioning (PassKit framework) the only supported approach for enabling contactless payment functionality on iPhone? What specific entitlements are required if the use case involves secure element communication for token provisioning (not bypassing Apple Pay)? We have already requested the relevant NFC entitlements through our Apple Developer account and are awaiting a response. Any guidance on the correct architecture and approval requirements would be greatly appreciated. Thank you in advance for your support.

Over the past few weeks, we have noticed a big difference in how well our App Clip App reads NFC tags compared to our Full App. The full app, which has the scan NFC button like all full apps, reads the NFC chips perfectly 100% of the time. The App Clip version of the same app has slowly started to be consistent in reading the NFC tags. Has something affected the App Clip NFC reading in the past few weeks after the iOS Updates? Can you tell us what we can do to make the NFC reading of the App Clip App as responsive as the NFC reading of the Full version of our App? Please advise because we want to make App Clip via NFC great, but not getting a consistent NFC read compared to the full NFC app is definitely a problem for consumers adoption.

Please help. We created a QR and NFC reader which will allow users to scan QR codes or Tap NFC tags and launch the appropriate experience. They keep telling us our app appears to be marketing our services. Makes no sense as this is a simple QR reader and NFC reader. Anyone have suggestions how to describe? We have seen a few others get approved with the similar utility. This can read any QR code and any NFC tag.

Hi,I observed that when approaching iPhone, with an NFC Scan session running (looking for NFC Tag), close to a NFC reader (any NFC reader or NFC Android phone for instance) triggers an abort of the session (I got NFC Scan Session Expired immediately).Does anyone knows if the is expexted behavior or a bug ?This prevents NFC interroperability of iPhone with device capable of both Reading/Writing tags and emulating a tag. As an example, a printer would read card for user authentication and emulating tag for smart connection.Regards,Jeremy.

Hello I am new in apple developer and I would like to know if I can make a loyalty program for my business using apple wallet. I send a request in order to issue some NFC passes using VAS protocol for our loyalty program: we will use it as virtual prepaid card in connection with our POS system (Zmenu of Zucchetti) Someone can help me?

Has anybody got access to Payment AIDs through Core NFC in Germany?Does the API look exactly the same as it does for the rest of Core NFC?How did you request access? Is there a contact form that can be used?Since Germany passed legislation in January it should now be possible to interface with Payment AIDs in germany. See:https://www.lexology.com/library/detail.aspx?g=01e51365-3e74-4fc4-ab84-0ef009d5ccfdhttps://www.lexology.com/library/detail.aspx?g=708875fd-3009-4708-855c-6df6dd30a3beI'd like to know how to request access or if it's generally available?

Hi, I'm trying to implement background NFC reading in my app, but I need it to work without associated url. On the tags should only be plain text that my app then works with. I only need this behavior if my app is active, so it shouldn't always open my app upon scanning. It should only retrieve data from a tag if the app is active, but without the user having to click on some button to trigger reading. If this isn't possible is there at least a way to intercept every nfc event and read it, like shortcuts currently does?

We've developed an app which performs data transfer with a control board over NFC. The NFC tag we're using is a type 2 NXP Ntag with 2k memory. The app works fine with models up to iPhone 11. However with iPhone 12 onwards, we've been experiencing constant NFC tag detection or NFC session termination failures. Moreover, when it fails one time, it keeps on failing for next consecutive attempts no matter how I hold the phone next to the NFC chip. I've tried all distances from 0cm to 4cm and all directions, nothing works. I'm confident that nothing's wrong in the NFC implementation since the same app works absolutely fine on other iPhone models with iOS versions ranging from 14.6 to 15. Is it something related to sensitivity of NFC transceiver? Is there any way it can be compensated at the source code?

We have been successfully writing to NFC tags using Beta 13, but have no luck with trying to lock them using the writeLock() function. After execution we get back a result of nil but it is definitely not locking. Any clues or has anyone managed to get this work as yet?Code is extremley straight forward (but might have done something stupid!) - Trying on different variations of a NXP NTAG213 tag:if (self.lockTag) { // locking required also os_log(Tag needs to be locked) tag.writeLock() { (error: Error?) in if error != nil { os_log(LOCK FAILED!!) session.alertMessage = Lock failed try again session.invalidate() } else { session.alertMessage = Write and Lock successful session.invalidate() } } } else { // only writing os_log(Tag is unlocked) session.alertMessage = Write successful! session.invalidate() }

Hello, Im trying to read data from an ISO15693 tag (M24LR64E-R from STMicroelectronics). Im using react native and react-native-nfc-manager - https://github.com/whitedogg13/react-native-nfc-manager/. Here my code when I send customCommand: tt// init manager t NfcManager.start() tt// waiting for a tag ttlet resp = await NfcManager.requestTechnology(tech, {t ttttalertMessage: 'Ready to scan tag't tt}); ttlet tag = awaitNfcManager.getTag(); const handler = NfcManager.getIso15693HandlerIOS() const flags = Nfc15693RequestFlagIOS.HighDataRate const customCommandCode = 0xb3 tt// some bytes const customRequestParameters = bytes.slice(2, bytes.length) tt// error with this cmd resp = await handler.customCommand({ flags, customCommandCode, customRequestParameters }) But I receive this error (throw exception): [CoreNFC] 00000002 83601300 -[NFCTagReaderSession transceive:tagUpdate:error:]:710 Error Domain=NFCError Code=100 Tag connection lost UserInfo={NSLocalizedDescription=Tag connection lost} Do you k

In my full application I have a universal link configured on an NFC tag that allows me to launch my application via NFC background tag reading and process additional NDEF records held on the tag via the NFCNDEFMessage provided to onContinueUserActivity(). I can use this same NFC tag to launch my App Clip via the same URL when the full app is not installed. However, unlike the full app the App Clip only receives a single NDEF record with .typeNameFormat = .empty. Is this a limitation of App Clip invocations? I have also implemented full NFC reader functionality within the App Clip which does retrieve all the records from the tag, but of course requires the user to tap the same tag twice to read its full contents. Ideally I would like to avoid requiring users to tap the tag twice to read.