Open cyberneid opened 1 year ago
I've seem a couple of reports that some phones/passports are more fussy with iphone NFC location and require a more accurate or closer position to the chip (no idea why), which seemed to start with iOS 16, and can lose connection with the chip on longer data reads. I can't replicate it here though so not really sure what I can do.
I am also looking at similar reports but without having been able to reproduce yet. I am interested in all reports, findings, or detailed test reports. (Note that enabling the iOS NFC wallet profile can provide more detailed and low-level iOS traces.)
I have experienced some frame delay timing violations on some iPhones in the past. Can the issue be related to a specific NFC chip variant in the phone?
Was the issue reported in the Apple Feedback system?
I've noticed this happen with my iPhone 15 Pro on one of my test passports. All other passports work fine except this one. However, the same passport works fine with an iPhone 11.
Note - The ReadID also shows the same issues with my iPhone 15 Pro so suspect either a CoreNFC issue of something odd with the NFC Chip! Will be raising a feedback with Apple.
Same here!
I have an iPhone 14 pro and I keep getting connection lost on SOD
and DG2
. But it works fine on my old iPhone 7+ and on the iPhone 11 from my work.
Starting from iOS 16, on iPhone 12, 13, and 14, we are experiencing a big issue with NFC. We are using it with Italian electronic identity cards, Azerbaijan electronic identity cards as well as other eid from other countries and passports as well.
With iPhone X, XR, and 7 it works like a charm
With iPhone 12, 13, and 14, the NFC reading starts but after BAC, during the reading of DG2 the NFC stops reading and returns this error:
Reading tag - DG11 Reading tag - DG12 Reading tag - COM Reading tag - DG1 Reading tag - DG2 [CoreNFC] -[NFCTagReaderSession transceive:tagUpdate:error:]:879 Error Domain=NFCError Code=102 "Tag response error / no response" UserInfo={NSLocalizedDescription=Tag response error / no response, NSUnderlyingError=0x2817c0120 {Error Domain=nfcd Code=29 "Tag Error" UserInfo={NSLocalizedDescription=Tag Error, NSUnderlyingError=0x2817c31b0 {Error Domain=com.apple.nfstack Code=20 "No response from tag" UserInfo={NSLocalizedDescription=No response from tag}}}}}
it is not a systematic error. Sometimes it works and the app reads all DGs, but very often we get that error.
We tried everything to understand the issue and to find a solution but with no luck.
Any suggestion?