Sample app fails to read German passport about nfcpassportreader HOT 5 OPEN

So, if I understand correctly, by just retrying multiple times you are able to make it work?.

Can you put logs with debug logs enabled? let reader = PassportReader(logLevel: .debug)

from nfcpassportreader.

Hi @danydev thanks for replying so quickly. I don't see an initializer for PassportReader(logLevel: .debug). In the sample app I am using version 2.1.1 of the package.

from nfcpassportreader.

you're right that's the old way to enable log level, that's not needed right now, you should already see\filter all kind of logs in the IDE.

@AndyQ do you find this kind of issue interesting? I mean, if ReadId is able to not fail, it probably does something slightly different? What it could be?
btw looks like the same issue reported here #166

from nfcpassportreader.

It is really interesting actually, and a little odd that it can read some of the items (so security and comms channels are setup correctly). The only thing I can really think of is maybe reading too quickly or too slowly (although not sure what I can do about that)?

I haven't yet though come across a passport that has this behaviour so I'm unable to test this out though.

from nfcpassportreader.

@NickAtGit as you can see it's really hard to try debug this remotely.
Can you scan like 6/7 times and post the full logs in separated files? It's a a bit a shot in the dark, but maybe, Andy can see something in the logs that could shed some ideas about tweaks to test out.

Also, what happens if you read only DG1, only DG2 and so on? Are you able to succesfully read them separately?
e.g.

passportReader.readPassport(mrzKey: mrzKey, tags: [.COM, .DG1], completed: { (error) in
   ...
}

from nfcpassportreader.