Display of UID and TagType

[erikm30]

Some apps, namely NFC Tools from wakdev and NFC NDEF READER https://itunes.apple.com/us/app/nfc-ndef-reader/id1286248064?mt=8 manage to show UID and TagType - see screenshots.
Any idea how to access these properties ?

[scottire]

UUID is possible by using the array foundTags from the session in
- (void) readerSession:(nonnull NFCNDEFReaderSession *)session didDetectNDEFs:(nonnull NSArray<NFCNDEFMessage *> *)messages

NSArray *foundTags = [session valueForKey:@"_foundTags"];
NSObject *tag = foundTags[0];
NSData *uuid = [tag valueForKey:@"_tagID"];

Accessing these is potentially insecure so best to have some verification in place with each valueForKey and accessed array.
I don't know if it's possible without doing sketchy access to these instance variables yet.

I don't have enough tags to get all the Tag Types, but there is an enum type beside tagID and from the CoreNFC header files it says that NFC Forum Tag type 1 to 5 that is NDEF formatted are supported.

[ttraub]

[EDITED] Thank you! That works. The _tagID value agrees with TagInfo and OmniKey Reader (initially I posted it didn't work, sorry)

[hansemannn]

I'll add it to the visual example, thanks!

[scottire]

@hansemannn Here is how I did it for phonegap-nfc:
https://github.com/chariotsolutions/phonegap-nfc/pull/287/files#diff-84fad93feff6a327c30a08cac8f546dfR171

[hansemannn]

The problem is that it looks like a private API and Apple will likely reject apps using that API. So besides the fact that the phonegap-PR might not get merged, I'm not sure if we should expose it as a best practice. Still wondering how the above apps got through review with that - probably obfuscated the call or Apple didn't catch it.

[Swati2707]

Hello,
I have been trying to read tag's UID with the sample app you provided. But its unable to read an empty tag's UID. My complete project is based on UID and I am unable to sort it out. https://drive.google.com/open?id=0B5RBua-pcqKwNzNUcVl5eXl0YXM

[scottire]

Apple will in fact reject an app that uses this private api. As for why you can’t read a non-ndef formatted tag, it’s because CoreNFC only detect tags that have properly formatted NDEF data.

[Swati2707]

Thank you. Let me find a way to encode it in some other way.

[Swati2707]

Hello,
Well my client is getting his tag NDEF encoded with URL. I haven't received the tags yet. But I have to confirm if i will be able to read the UID of those tags. As I have noticed NXP app and want to know more about it. Can anyone help?

[erikm30]

You can use the NDEF itself to transfer ("Mirror") the UID to the phone. (i.e. encode https://your.customer.com/some_path/uid/ resp. https://your.customer.com/some_path?uid=xx..xx). In case of NTAG 213 and other NXP tags, you can encode even "00..00" for all tags and let the mirror feature do the job of displaying the actual tag UID. Seems that Apple is actively blocking features outside NDEF reading (see changelogs of some of the reader apps that had it before)., Regards erikm 2017-11-02 6:45 GMT+01:00 Swati2707 <notifications@github.com>:

…

Hello, Well my client is getting his tag NDEF encoded with URL. I haven't received the tags yet. But I have to confirm if i will be able to read the UID of those tags. As I have noticed NXP app and want to know more about it. Can anyone help? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAxMcRp0lTZUJ_bjiAAGccgnT35P_NaCks5syVcGgaJpZM4PfDhe> .

[Swati2707]

Hey. Thank you so much erikm30.

[kkscwcd]

@erikm30
I am trying the same things but getting only payload and ID is always coming blank in my APP . When i used the NXP from Itunes store it read the ID . Can you please share the code for this which you mentioned above .

You can use the NDEF itself to transfer ("Mirror") the UID to the phone. (i.e. encode https://your.customer.com/some_path/uid/ resp. https://your.customer.com/some_path?uid=xx..xx). In case of NTAG 213 and other NXP tags, you can encode even "00..00" for all tags and let the mirror feature do the job of displaying the actual tag UID.

Please share some code for mirroring features so i can understand.

[erikm30]

Also the next release of NXP TagInfo has to remove the ID from being displayed, just like the other apps. What I was referring to was a feature of the ICs - you can personalize them in such a way, that the NDEF contains the UID and make use of that. 2017-11-16 5:41 GMT+01:00 kkscwcd <notifications@github.com>:

…

@erikm30 <https://github.com/erikm30> I am trying the same things but getting only payload and ID is always coming blank in my APP . When i used the NXP from Itunes store it read the ID . Can you please share the code for this which you mentioned above . You can use the NDEF itself to transfer ("Mirror") the UID to the phone. (i.e. encode https://your.customer.com/some_path/uid/ resp. https://your.customer.com/some_path?uid=xx..xx). In case of NTAG 213 and other NXP tags, you can encode even "00..00" for all tags and let the mirror feature do the job of displaying the actual tag UID. Please share some code for mirroring features so i can understand. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAxMcdiQv-RhasfrDPwj1-ZgnsXGQxZFks5s27z1gaJpZM4PfDhe> .