Fails on chinese passport about nfcpassportreader HOT 4 OPEN

Not all passports follow the ICAO standard regarding listing Datagroups in the COM's 5C tag. They actually list some elements in the COM 5C tag that is not in the ICAO-standard.

This should perhaps not give an error, as reading the passport itself should be fine.

Perhaps a solution here could be to return the PassportModel in the callback instead of an error, and add a "warning/errors" parameter to the Model so consumers can be notified of the deviations that has occured.

So what actually happens here is that a DG-group is listed in the COM, but it does not actually exist. So it should be skipped instead of throwing

from nfcpassportreader.

I have noticed this too. There can be 19 DataGroups but the app only supports to 16. Try and add DG17-19 with no parsing.

from nfcpassportreader.

I have noticed this too. There can be 19 DataGroups but the app only supports to 16. Try and add DG17-19 with no parsing.

Theres no official documentation on those datagroups.

i will try to create a pr for this when i have the time

from nfcpassportreader.

@iAbdul could you try again with the branch on the PR above and see if this fixes it for you?
@advatar did you have any documents you could try on? Testing is much appreciated as i dont have any documents on hand.

Please comment in the PR so that if/when @AndyQ eventually gets around to it he can see that the fix is verified.

from nfcpassportreader.