Error Reading URLs #11
Replies: 3 comments 6 replies
-
|
Can you provide a debug log or maybe just a screenshot from a phone of the tag as read by NFC tag info or similar tool? If you add a title to the URL you write, it gets converted into a smart poster, and those are explicitly not supported (but you should get a warning about that specific use) |
Beta Was this translation helpful? Give feedback.
-
|
Absolutely! Here are screenshots from the program while debugging and from
a phone with the NFC tag info.
…On Thu, Mar 28, 2024 at 2:14 AM Martin Paljak ***@***.***> wrote:
Can you provide a debug log or maybe just a screenshot from a phone of the
tag as read by NFC tag info or similar tool? If you add a title to the URL
you write, it gets converted into a smart poster, and those are explicitly
not supported (but you should get a warning about that specific use)
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2VWXW5KFHNMXBW5422AFXTY2OYNNAVCNFSM6AAAAABFMD62DKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSMZXGAZDE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
You missed pics |
Beta Was this translation helpful? Give feedback.
-
|
Apologies! |
Beta Was this translation helpful? Give feedback.
-
|
This looks like a bug/parsing issue, will look at why the header parsing fails. |
Beta Was this translation helpful? Give feedback.
-
|
Could you give this build a spin: https://github.com/martinpaljak/nfc4pc/actions/runs/8478097132/artifacts/1369085659 |
Beta Was this translation helpful? Give feedback.
-
|
as I think this was a bug that already caught my attention during testing but has not turned into a release. 1523e2f |
Beta Was this translation helpful? Give feedback.
-
|
Works perfectly! Thank you so much for the time and effort! |
Beta Was this translation helpful? Give feedback.
-
|
OK. I'll prepare a new release at some point, but there is no ETA. |
Beta Was this translation helpful? Give feedback.
-
First: Great tool! I appreciate all of the documentation and help you provided!
This might be user error, but whenever I try to read NTAG215 tags using an HID OmniKey 5022 USB reader, running version 23.07.10 of the program on both MacOS and Windows 10, I obtain the error "# WARNING: No URL found in tag with UID #, use -u to specify UID URL" (which is expected if the tags did not have URLs written on them; "UID #" is replaced with the unique UID tag identifier for the specific tag whose URL I am attempting to read and open).
However, I have written, rewritten, and re-rewritten URLs on multiple tags, using different NFC writing tools, only to see this same error message when attempting to open them with the NFC4PC program. I also double-checked that the URLs are correctly written by successfully reading and opening them on an iPhone (however, I do recognize iPhone NFC software integration is quite different than this program on Windows/MacOS). All other NFC4PC program functionality, including browser navigation and specific argument lines work perfectly!
Do you have any specific instructions on 1) URL formats for this program (i.e. is there a different format to follow than what is common on NFC writing programs like NFC Tools or NFC21 Tools) or 2) any workaround to read/open these written URLs? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions