Error "Not valid NDEF records found" when trying to select a CSV in TagWriter for Android

[bilbo]

I have TagWriter version 5.0.0. on my Android phone.
Downloaded and installed from the PlayStore today.

I have several CSV files I have copied to my phone.
The CSV files were created using Excel and were saved in MSDOS-CSV, and Windows-CSV, and also as text file with CSV file extension.

My objective is to send the CSV file contents to an NFC Chip.
I have confirmed I can successfully send the text to the chip using TagWriter if I first copy the contents of the CSF file and paste the text into the Text option in TagWriter.
So I know the tag and phone are compatible with TagWriter.

However, when I try to open any of CSV files, in ANY format, I always get the same error:
"Not valid NDEF records found."
And to be clear, I am getting this error when I try to open the CSV file, LONG BEFORE I could even try to send it to the NFC chip.

Please help.
What am I doing wrong and how can I fix this?

[EduardoZamora]

Hello @bilbo

Hope you are doing well.

Could you please try creating an Excel file with a structure like the following and saving it as CSV?

Also, you may refer to TagWriter User Manual, Section 6.2 for more information on this.

Please, let me know your findings.

Regards,
Eduardo.

[bilbo]

Thank you for the information and the link.
It does solve the problem with CSV files.

However, I must still be missing something though.
The only data that gets written to the tag is the top row.
Each subsequent tag gets the next row and so on.

HOWEVER, it ONLY writes the top line of text from that row.

For example:

TEXT_RECORD	Row_1 Row_2	en
TEXT_RECORD	Row_1 Row_2	en
TEXT_RECORD	Row_1 Row_2	en

In this example, ONLY the "Row_1" from each record gets written to the tag.

[EduardoZamora]

Hi,

For this procedure, only one row per cell would be allowed. An example of this can be found in TagWriter User Manual, Section 6.2, item "1)".

Regards,
Eduardo.

[bilbo]

I'll need to read and test this but recently tested positive for COVID so it's going to be a little while...