NFC (ISO7816)- Tag Connection Lost IPhone 15 & 16 variants

Question

Created Oct ’24

Replies 2

Boosts 1

Participants 3

NFC reading starts but after BAC, during the reading of DG2 the NFC stops reading and returns with Tag connection Lost error . It almost fails everytime on iPhone 15 Pro max with the following error. What's the solution for this?

This is really important because our app entirely relies on the NFC data to proceed forward. This always fails in iPhone 15 & 16. Same card works fine on older iPhone models. What change should we do or include for the newer models.

 Error Domain=NFCError Code=102 "Tag response error / no response" UserInfo={NSLocalizedDescription=Tag response error / no response, NSUnderlyingError=0x303bd6af0 {Error Domain=nfcd Code=29 "Tag Error" UserInfo={NSLocalizedDescription=Tag Error, NSUnderlyingError=0x303bd6910 {Error Domain=com.apple.nfstack Code=20 "No response from tag" UserInfo={NSLocalizedDescription=No response from tag}}}}}

Boost

Answer 1

Engineer OP

Apple

Oct ’24

There is not enough information to determine what the problem might be here.

My first question would be how long into the reading session is this happening? Is this happening with one tag, or one kind.brand of tag? Have you tried different tags?

In any case, filing a Feedback report with some logging will be the best way for us to investigate the issue further.

First, please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Wallet for iOS to install a logging profile on your device.

Once that is installed, then reproduce the issue. Once reproduced, then follow the instructions at the above link to create a sysdiagnose

Then use the Feedback Assistant. to create a report and include a detailed description of the issue, details of the tags you are using, and the sysdiagnose from the above step.

Also include the following info:

What is the setup on the device. Including apple wallet settings
Please provide sample app if you have one, or can create one
Video capture of the failure scenario. Including approx timestamp
the Bundle ID of the app you have tested this with

Then please post the FB number here for my reference.

If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why?

Argun Tekant /  DTS Engineer / Core Technologies

0

Answer 2

Ger Teunis OP

Oct ’24

We can confirm this behavior as well. iOS 18.1 beta 7 (public beta 4) seems to have solved this issue for us. @mnive93 can you confirm this as well?

0