Reading UIDs of NFC Cards in iOS 13

Question

I would like to retrive the UID of MiFare cards. I\'m using an iPhone X, Xcode 11 and iOS 13.

I\'m aware this wasn\'t possible (specifically reading the UID) until

Answer 1

In iOS13 I was able read the Tag.identifier value for various MIFARE family's DESfire and UltraLight tags same as @scott-condron's answer, but for various MIFARE Classic ICs (the unknown family member?) my Console shows different error types.

Perhaps private framework APIs similar to the iOS11 work-around in the hack you mentioned would be helpful in these cases, e.g. to intercept and amend the discovery polling routine, but I wouldn't know which ones or how to use them.

Below you can find some test results for MIFARE Classic 4K (emulation) tags, as also reported in this github thread and this MIFARE support thread. Following Table 6 of Application Note #10833, the Select Acknowledge (SAK) value of 0x38 of the emulation tags below translates into 0 0 1 1 1 0 0 0 for bits 8..1, i.e. bits 6, 5, and 4 are 1, and therefore these SAK values classify as Smart MX with CLASSIC 4K as per Figure 3 of Application Note #10834.

1. an Infineon Classic 4k Emulation successfully logs 1 tags found with the correct UID (31:9A:2F:88), ATQA (0x0200), SAK (detects 0x20, i.e. ISO 14443-4 protocol, and 0x18, i.e. MIFARE 4K, both part of the expected value: 0x38) and respective tag type (both Generic 4A and MiFare classified correctly), but then throws a Stack Error:

   error   14:48:08.675369 +0200   nfcd    00000001 04e04390 -
       [NFDriverWrapper connectTag:]:1436  Failed to connect to tag: 
       -{length = 8, bytes = 0x7bad030077180efa} 
       { Tech=A Type=Generic 4A ID={length = 4, bytes = 0x319a2f88} 
       SAK={length = 1, bytes = 0x20} ATQA={length = 2, bytes = 0x0200} historicalBytes={length = 0, bytes = 0x}}
   :
   error   14:48:08.682881 +0200   nfcd    00000001 04e04390 -
       [NFDriverWrapper connectTag:]:1436  Failed to connect to tag: 
       -{length = 8, bytes = 0x81ad0300984374f3} 
       { Tech=A Type=MiFare ID={length = 4, bytes = 0x319a2f88} 
       SAK={length = 1, bytes = 0x18} ATQA={length = 2, bytes = 0x0200} historicalBytes={length = 0, bytes = 0x}}
   :
   default 14:48:08.683150 +0200   nfcd    00000001 04e07470 -
       [_NFReaderSession handleRemoteTagsDetected:]:445  1 tags found
   default 14:48:08.685792 +0200   nfcd    00000001 04e07470 -
       [_NFReaderSession connect:callback:]:507  NFC-Example
   :
   error   14:48:08.693429 +0200   nfcd    00000001 04e04390 -
       [NFDriverWrapper connectTag:]:1436  Failed to connect to tag: 
       -{length = 8, bytes = 0x81ad0300984374f3} 
       { Tech=A Type=MiFare ID={length = 4, bytes = 0x319a2f88} 
       SAK=(null) ATQA=(null) historicalBytes={length = 0, bytes = 0x}}
   :
   error   14:48:08.694019 +0200   NFC-Example 00000002 802e2700 -
       [NFCTagReaderSession _connectTag:error:]:568  Error 
       Domain=NFCError Code=100 "Stack Error" UserInfo={NSLocalizedDescription=Stack Error, NSUnderlyingError=0x2822a86c0 
       {Error Domain=nfcd Code=15 "Stack Error" UserInfo={NSLocalizedDescription=Stack Error}}}
   

2. an NXP SmartMX (Classic 4k emulation) with UID CF:3E:40:04 is discovered initially, but a reception error during ISO 14443-4A presence check (Proc Iso-Dep pres chk ntf: Receiption failed) continuously restarts the discovery polling until the session finally expires, possibly preventing the other SAK value 0x18 (for MIFARE 4K tag type) to be received:

   error   10:44:50.650673 +0200   nfcd    Proc Iso-Dep pres chk ntf: Receiption failed
   :
   error   10:44:50.677470 +0200   nfcd    00000001 04e04390 -
       [NFDriverWrapper disconnectTag:tagRemovalDetect:]:1448  Failed to disconnect tag: 
       -{length = 8, bytes = 0x07320d00f3041861} 
       { Tech=A Type=Generic 4A ID={length = 4, bytes = 0xcf3e4004} 
       SAK={length = 1, bytes = 0x20} ATQA={length = 2, bytes = 0x0200} historicalBytes={length = 0, bytes = 0x}}
   default 10:44:50.677682 +0200   nfcd    00000001 04e04390 -
       [NFDriverWrapper restartDiscovery]:1953
   

3. an actual NXP Classic 4k with UID 2D:FE:9B:87 remains undetected and throws no error. The discovery polling session for this tag simply times out after 60 seconds and logs the last 128 discovery messages transmitted (Tx) and received (Rx), among which the following pattern is repeated (which does include the expected UID: 2D FE 9B 87):

   error   11:42:19.511354 +0200   nfcd    1571305339.350902 Tx  '21 03 07 03 FF 01 00 01 01 01 6F 61'
   error   11:42:19.511484 +0200   nfcd    1571305339.353416 Rx  '41 03 01'
   error   11:42:19.511631 +0200   nfcd    1571305339.353486 Rx  '00 F6 89'
   error   11:42:19.511755 +0200   nfcd    1571305339.362455 Rx  '61 05 14'
   error   11:42:19.511905 +0200   nfcd    1571305339.362529 Rx  '01 80 80 00 FF 01 09 02 00 04 2D FE 9B 87 01 18 00 00 00 00 2D 11'
   
   error   11:42:19.512152 +0200   nfcd    1571305339.362734 Tx  '21 06 01 00 44 AB'
   error   11:42:19.512323 +0200   nfcd    1571305339.363959 Rx  '41 06 01'
   error   11:42:19.512489 +0200   nfcd    1571305339.364028 Rx  '00 1D 79'
   error   11:42:19.512726 +0200   nfcd    1571305339.364300 Rx  '61 06 02'
   error   11:42:19.512914 +0200   nfcd    1571305339.364347 Rx  '00 00 EB 78'