Hmm…
-
the xDF2 is a DESFire EV2 chip not a DESFire EV1 chip. The EV2 is backward compatible, but I believe there are commands that are needed to set up EV1 style AIDs (applications) that are not the same as commands for the EV1… so the system would need to understand the proper commands to init AIDs on the EV2 chip.
-
if there is no reaction from the reader, are you sure it is able to read the xDF2? if you purchased a blank DESFire EV2 card from somewhere and tried it, would the reader blink and beep or remain silent? Some readers are configured to do absolutely nothing if the chip being read is invalid… this is a security choice, so it may be configurable in the SMS… but my hunch is that the problem has to do with the antenna in the reader being too shit to read the xDF2.
-
do they purchase the EV1 cards from the SMS vendor or do they just buy blanks off Amazon or something? it may be that the EV1 cards they purchase are pre-initialized with the proper AIDs. if you can get a “new” EV1 card that has not been touched yet and scan it with TagInfo, perhaps there are AIDs on it already?
-
iPhone will not react at all unless A) you have iOS 13 and an NFC app that reads raw NFC tags, or B) the tag has an ndef record on it. The xDF2 does not come with the standard Type 4 NDEF AID so there is no NDEF record, so most all NFC apps for iPhone will just stare at you blankly when you try to read it. The apps are not even told there is a tag in the field if there is no NDEF record on the chip.