I'm facing issue on my NFC app such that the 'SendMiFareCommand()' API returns 'Tag Connection Lost' or 'Tag No Response' errors very frequently, especially on iPhone 12 and above, where 5G signal is weak. Since the issue doesn't appear on older iPhones or even on newer iPhones when they're put in flight mode, with exactly the same setup, we're certain that it has got to do something with the way iOS handles NFC function when 5G signal reception is poor. We even got this seconded from NFC tag manufacturers NXP and ST. So is there any way I can adjust priority / precedence of NFC function when 5G signal reception is poor? With 5G signal poor in almost all areas of the US as of now, this issue is pressing and affects the entire UX of my app.

I'm developing an NFC based app where I've been facing issues such that 'Tag Connection Lost' or 'Tag no response' errors are returned by the 'SendMiFareCommand()' function very frequently. This is observed more frequently on iPhone 12 and above when 5G network signal is weak. Anyway, that's a different issue which I'm following up separately. Because of those frequent errors, I require to Invalidate() NFC session and restart a new session because those errors are non-recoverable. For this purpose, I invoke 'InvalidateSession()', check for session.IsReady flag to be 'false' and then start a new session for the retry. Right after calling 'BeginSession()' at this moment, 'DidInvalidate()' gets hit with an NSError code 'System Resource Unavailable'. What could be the cause behind? I'm checking if previous session was properly invalidated.

To read from an Mifare Ultralight tag (NTAG I2C Plus), I'm using NFCMifareTag.sendMifareCommand method. It works most of the times, but I randomly get errors of types: Tag Response Error / Tag No Response Tag Connection Lost Stack error Moreover, these errors ar eobserved way more frequently on iPhone 13 Pro max model than any other iPhones, not sure why. This is the code block for reference: miFareTag.SendMiFareCommand(tagCommand, completionHandler: (nsdataObj, error1) => { if ((error1 == null) && (nsdataObj != null)) { readSuccess = true; } else { readSuccess = false; // here error1 prints Tag response error or Tag no response or Tag connection lost or Stack error } }); Has anyone observed these errors and knows ways to avoid them? I could not find any documentation on any of these error types. Can someone guide me?

I'm working on an NFC app for R&W operations on an NFC tag. All R&W operations work fine with the 'SendMiFareCommand()' API, however there's a special command for 'password authentication' feature where it fails with a timeout, may be because the NFC tag is not responding in time. This issue is not observed every time, so I'm sure about the command I'm sending nd how its response is to be processed. Moreover, this issue appears more frequently on iPhone 12 & 13 than older ones, may be because they changed something at the NFC lower layer. Anyway, Android allows adjusting timeout which is usually done before sending any command, so that it gets enough time to respond and the session remains active. It's typically done as - mifareTag.Timeout = timeout_value_ms; Can this be done for iOS? What is the default value of the timeout? If timeout cannot be modified, is there any alternative to allow enough time for the NFC chip to respond to the commands being sent from the app? I could not find anything about this in the documentation.

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?

I want change display name of the app (the one which is displayed below the app icon on user's device). I do not intend to change the app's name or its bundle identifier. I know how to do it, but want to know if this will also affect the URL of my app on the app store? Reason I ask this is I already have published QR codes directing to my app on the app store. If changing the app's display name is also going to change these URLs, then I will need to publish new QR codes.