“nfc”

Also related to testing iOS communicate using the ISO-7816 protocal to a PN7150 device;If I have iOS initiate the NFC-Scan while it is already in the RF-Field of the PN7150 device,the communication will fail more than half of the time with an Error ofDomain=NFCError Code=104 Tag is not connectedAnd the XCode Debugger console showing the following trace-output;2019-10-31 13:40:35.397849-0400 NFCTagReader[381:37470] [CoreNFC] 00000002 80436f00 -[NFCTagReaderSession _connectTag:error:]:573 Error Domain=NFCError Code=100 Stack Error UserInfo={NSLocalizedDescription=Stack Error, NSUnderlyingError=0x2824989c0 {Error Domain=nfcd Code=29 Tag Error UserInfo={NSLocalizedDescription=Tag Error}}}If I have iOS initiate the NFC-Scan outside of the RF-Field of the PN7150 device, then bring it into proximity of it,then communication will succeed the majority of the time.Does this behavior make sence?Should iOS always initiate a scan away from an NFC-Device it is to communicate with, then be brought

While I want Apple to support this natively, this may be possible using a small NFC tag under your phone's case or attached to the back. Something like this: https://taptag.shop/products/tap-tag-hyperslim. (The price is ridiculous, but I guess they know they have a niche thing that people want.) It essentially doesn't use the iPhone's NFC chip. I don't have one of these (yet) and am not sure if this would affect Qi charging or have any other ill effect.

I have the same problem. iPhone 13 mini. NFC is completely dead. Apple Pay on web is working fine. On physical terminals the phone does not recognise card reader nor is able to recognise any NFC tag. What is worse - we have tried another 3 iPhones with the same IOS version and everything is fine so not sure what is the pattern here. I was communicating this to apple support and they run diagnostic - no problem found. No workaround like resets are working.

In the WWDC 2019 Video on NFC enhancement , he said “iPhone 7 or future phones”. No mention of iPod Touch or iPad devices.

I found what the problem was. It's not obvious, but the default payment app settings are hidden until the user grants NFC permission to the app.

Have you found a solution to your problem? It might be an error with the NFC certificate? the fact that the Automatically Select dialog is shown could tell otherwise tho.

I found another app using NFC and it does have the same delays now with the new iOS update.I appreciate your assistance. I will file a bug.Thanks,

I'm trying the same thing also, but Apple did not think on this. It was very useful if we could set something in wallet to act as an regular NFC card.

This still occurs in iOS13.3. I stopped having SIGABRT after supplying an entry for Privacy - NFC Scan Usage Description in the info.plist. Crazy!

I can't believe this is not possible yet. This would be the most conveninet way to trigger NFC tags for HomeKit automations. Please, Apple, enable it.

Hi! Which way you read Ultralight card? Is it an Apple sample or your own sourcecode thst uses Core NFC? Could you please share it?

Same issue. Can’t read any NFC enabled document anymore. Weird how can you break a functionality like this and not notice it at all.

Hi,I have had good readings from NFC since Beta 3, are you not getting any response from any tags?Maybe you have the wrong type of tags

Same issue here. Weird thing is that dependency that uses CoreNFC installed via CocoaPods works. But breaks when I try to scan nfc

Not able to read data from the NFC tag using SendCommand . the entitlements and info.plist values are in place.I am able to create a session and connect to the tag.