We purchased NTAG215 tags specifically because they support up to 540 bytes of NDEF data. We spent more than 200 EUR on these tags to ensure that our long verification URLs would fit without any issues.
However, the NXP TagWriter app refuses to import our CSV file and always reports “Invalid format”. The CSV structure is correct (RecordType,URI), the file is saved as UTF-8 with BOM, the URLs are valid, and the tags have enough memory. The same data can be written manually to a single tag without any problem. The issue only happens during CSV import.
This means the limitation is not the tag, not the URL, and not the CSV format. The limitation appears to be inside the TagWriter app itself.
It is extremely frustrating that after spending this amount of money on official NXP tags, we cannot use the official NXP app to batch-write them. We should not be forced to buy a third-party app just to perform a basic operation that TagWriter claims to support.
We need clarification on the following points:
Why does TagWriter reject valid CSV files when the URL length is within the NTAG215 memory limits?
Is this a known limitation or a bug in the CSV import function?
Is there an official workaround that does not require paying for another app?
We urgently need a solution, because we purchased these tags specifically for this use case.
and my URL is looking like this:
https://200.410.222.111:4443/verify-status.html?work_id=9d611323a-a9ac-4fb9-9039-74f443cf2720&sig=MK...
thank you, but now he shows nothing. No error but also no data. It looks lik this for testing - normal case we have much longer URL
Hello sir,
I was checking your CSV file, there are some fields that you need to add to your structure.
Please refer to the following community case: Error "Not valid NDEF records found" when trying to select a CSV in TagWriter for Android - NXP Comm...
In the User Manual, please check the description of 3) LINK_RECORD.
Have a great day, sir!
Hello,
Could you please confirm whether you are able to successfully read a short link from the NDEF?
I ask because, if this is working, it is very likely that the issue lies in the NDEF structure itself. Please note that, according to the NFC Forum specification, there are both Records and Short Records. If your payload size exceeds 255 octets, it is possible that the NDEF has not been constructed correctly.
I recommend reviewing the NFC Data Exchange Format specification available on the NFC Forum website.