what tool to write a proper 2.1 formatted VCF file to a tag , have tried using NFC tools pro, tag writer on android with no success ( ie file doe not open in contact etc on android ) when written as a text or file.This tag is formatted under 2.1 vcf format and opens porpely in contacts on windows.
What options to use to write a vcf file in NFC tools or tag writer so that it opens in contact once scanned.
A very puzzling question to me as this should be obvious but i have tired all the above with 0 success in reading it.
In tag writer there is an option to write the vcf imported in contacts via business card option, but here the size strangely increases when a BASE64 photo is encoded.
The problem might be with the way the data is being stored, but more likely it’s the opening process. Let’s start with some screenshots from taginfo that show how you’ve stored the data, then we can move on from there. Redact any data you don’t want to share.
Hi Amal sorry my bad it seems I did not explain. My situation properly.
it’s a custom handcoded VCF file with BASE64 encoded image and iam trying to write the created vcf file on the nfc tag using tag writer and nfc tools.
To elaborate further
These encoded vcf files with photo write fine as a file or text option in tag writer but these written file won’t open as contact in android when detected. When. Scanned they show tagwiter or taginfo as apps to open it.
On the other hand
I don’t have any issue in writing a business card via the internal options of tagwriter or nfc tools, they write fine and open fine in contacts on android when scanned.
Hope iam able to put it correct for experts here to point me in right direction
I think the problem is that there is no VCF record type NDEF records. The record type for vCard is well known and the phone knows what to do with it when opening that type of record from an NFC tag. Because file storage is not a design goal for NFC, you might be able to write the binary data to the NFC tag, but the phone isn’t going to know what to do with it.
You could use a special application to read the data and properly create the contact file and then try to import it into Android contacts, but because it is not a native NFC well-known NDEF record type, you’re not going to get native support for that kind of data on an NFC tag.
I guess the other question I have is why do you need VCF file format? You can easily embed a photo into vCard NDEF records. Essentially they are the same but the vCard NDEF record type is critical for ensuring the phone understands the data contained in the record is a vCard.
Nope thats the issue I am not able to write it using tagwiter by selecting contact as the size becomes bloated in contacts when I import the vcf card as contact import, so the only option is to write the NDEF directly on the tag as my vcf file with WEBP. Embedded photo is just about less than 700 byte.
The same when imported in contacts via vcf import turns to about 3000 byte that’s the issue.
Any other ideas to keep the size less than 700 byte as thats the size of my Embedded vcf file with photo.
How have others done in on n216 tag, or am I over attempting at my end, iam sure there is way to push the small less than 700 byte payload directly in it., iam clear missing something by using tagwiter and nfc tools