BUG: NFC Card Reading Fails When Multiple AIDs Are Configured

[MartinAtStagnation]

NFC Card Reading Fails When Multiple AIDs Are Configured

Bug: getCardCommands fails when Info.plist contains additional supported NFC AIDs

Summary

The NFC library fails to read card information when the iOS app is configured to support more NFC Application Identifiers (AIDs) than the library's Idemia and Thales card command implementations support.

Steps to Reproduce

1. Add additional AIDs to Info.plist under com.apple.developer.nfc.readersession.iso7816.select-identifiers before the library's supported AIDs. For example: (Order is important)

   • A0000002471001
   • A00000045645444C2D3031
   • A000000077010800070000FE00000100
   • A0000000181002030000000000000001

2. Use an NFC card that supports both an additional AID and one of the library's supported AIDs

3. Attempt to read the card

[ambrose40]

Right now library is targeted to support Estonian Idemia (Cosmo 8.1, Cosmo 8.2, Cosmo X) and Thales ID1 NFC card chips.
Supported AID and related APDU commands are specific for those officially supported cards.

Use an NFC card that supports both an additional AID and one of the library's supported AIDs

Not clear what card is supposed to support both additional AID and one of the library's supported AIDs?

[MartinAtStagnation]

Thank you for the response.

From what I understand, a single Estonian ID card chip can contain multiple applications and respond to multiple AIDs. So when iOS scans the card, it picks the first AID from the Info.plist list that the card supports and sets that as tag.initialSelectedAID—which may not be the AID the library expects, even though the card also supports the library's AIDs.

I've tested this with my Estonian ID card (date of issue: 30.08.2024). Our app uses additional AIDs for another library, and when scanning my card, iOS detects and selects one of those AIDs first instead of the Idemia/Thales AIDs that this library supports.

For more details: A0000002471001 - that was the AID, the iOS detected for my card.

However, the reader worked fine on a card, that was issued on June 2021

[metsma]

I think their application supports e-MRTD documents and its AID is selected before, because cards have also e-MRTD applications on it.

[ambrose40]

I have registered internal ticket (NFC-108) for improvement, shall be fixed in future release.

[ambrose40]

POC fix in PR #9.