-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Read data example not decoding NDEF records #11
Comments
Took me a longer than hoped this evening as I was having some USB UART cable issues, but I was finally able to take a look at this, and after some digging, it appears the structure I used to send to I've updated the README and |
Hey @techniq, thanks so much for the quick response. By using |
I wrote my tag using am Android app as well. Getting ready to call it a On Mon, May 23, 2016, 11:35 PM Katy Moe notifications@github.com wrote:
|
No problem. Thanks for your help. I've just discovered that for some reason, writing only one NDEF record causes the problem, but if I have two NDEF records it's fine. I'm happy with that workaround. |
It looks like |
Yes, I was still passing an array. |
If you could send me the logs with |
Using the read_data.js example, I can't get it to show the parsed NDEF records. It correctly displays the buffer data, but the next line seems to fail silently.
I've tried with NTAG216 and various Mifare cards.
Here's the log:
Would you mind double checking this still works for you? The ndef dependency may have changed. I appreciate that this is a side project, and I'm willing to help patch things up if you need me to.
The text was updated successfully, but these errors were encountered: