Post

Replies

Boosts

Views

Activity

Reply to iOS 14 CoreNFC ISO15963 Authenticate command.
Hello, thank you for your reply. Yes I have the complete APDU from the manufacturer, but I am not sure how this "authenticate" command includes the 0x35 or the other parts of the APDU such as the selection of the Key. The APDU for 0x35 includes a flag 0x20 which tells the chip we will be sending the tag's UID, and also the Key number from inside the chip so it can perform the AES encryption process. I have tried a bunch of combinations, with chip UID, without chip UID, sending the whole APDU. But I just get one of two errors: Tag connection lost or Code=15 "Stack Error" Oh and btw, yes I am using NFCTagReaderSession and confirming its a ISO15963 tag I am able to send: getSystemInfo and get the correct tag information.
Jun ’20
Reply to iOS 13 CoreNFC ISO15963 customCommand 0x35
Apple just released their new beta version. It seems they have implemented authenticate command 0x35 for ISO15963. But there is no much more information on the documentation as to how to implement this yet. In a few more days there will be a WWDC2020 presentation of this and other commands they have implemented. Hopefully there we will get more information and finally get this apps on everyone's hands!
Jun ’20
Reply to iOS 13 CoreNFC ISO15963 customCommand 0x35
I have submitted a feature enhancement request on Feedback Assistant last year. It has been slow, but we already sent chip implants to Apple Engineers and private documents of how this chips work. They have everything to make the necessary changes. We have not hear back from Apple NFC Engineers since a while ago. Last word we had was that they needed an example data for the chip and what to expect from the chip. We have provided that and still waiting for their response on Feedback Assistant. We are still waiting and periodically messaging them to see if there are some news.
Jun ’20