TagReader keeps failing on reading DG2 from older dutch passport. about nfcpassportreader HOT 4 OPEN

iOS invalidates the NFC session after a certain time out. How ReadId can read it quicker (to avoid this issue) I do not know.

It also isn't only Dutch passports, but there are more documents that are slow enough that the entire transaction takes too long.

from nfcpassportreader.

iOS invalidates the NFC session after a certain time out. How ReadId can read it quicker (to avoid this issue) I do not know.

It also isn't only Dutch passports, but there are more documents that are slow enough that the entire transaction takes too long.

True! Sorry for the confusion, I should have been clearer. The log that I shared repeats itself about 3 or 4 times at "Reading DG2...". It seems like the package is having trouble reading the DG2 data from passports of these years and keeps retrying before iOS invalidates it. (I also updated my description)

from nfcpassportreader.

The method to read a datagroup is to sent a select-command. That command is then followed by 1 or many read-command. After the first read command, the first bytes are read to see how long the DataGroup is and based on that it will repeatedly sent more read-commands. The read-command only reads 160 bytes in your case. DG2 is about 4KB, so it will do that several times.

Those few lines says a lot about that "repeating":

TagReader - Amount of data left to read - 3672
data bytes remaining: 3672, will read : 160

So in your case, it would have repeated that for another 22 times if iOS didn't "Invalidate Session". As much as I would love this fixed and know how to either make iOS not do that or how to make it read quicker (or the reading handling this and reconnecting and continuing where it left off), nothing in that log is anything that shouldn't happen.

It isn't retrying!

from nfcpassportreader.