Reply

Hello,

1. As far as I know, iPhone Contacts app doesn’t support vCard4 format, it works with vCard3, and it has no proper support for encoding. I remember seeing that some other apps for iPhone have support for vCard4 format, but I don’t use iPhone, so I don’t know which.
2. WIndows Contacts and Outlook support all vCard formats, but it can’t import UTF-8, and to work with character encoding, it has to use vCard 2.0 format which has very strange encoding. Microsoft forums are filled with bug reports about this, and that is the issue for years, and still, vCard support in Windows Contacts and Outlook is very spotty.
3. Android phones, before Android 10 were not properly reading vCard4, Android 10 and newer all fully support it. Android can’t import image via provided photo URL.
4. vCard4 only supports UTF-8 encoding, it can’t be anything else. So, it properly encodes everything, including cyrilic or chinese.
5. I have tested extensively both vCard formats, and all fields are working, including phone and email. I have few very complex vCards using different charsets (french, german, cyrilic), with all fields included.
6. Sign + in phone number works fine, but you need to enter number without any spaces, that is vCard specs requirement. But, I tested phones that have empty spaces, and Android phones imported them correctly.
7. Label and Notes fields are all correct, again, I have tested all that, and I used it few times. One of the reasons I know it works, is that in the first plugin version when vCard4 is added, few users had issues with Notes field, and I have fixed it.
8. Best way to see that everything is correct, you can download VCF. Widget has option to show contet that includes download link, and via that link you can download VCF file to computer and see the content.
9. vCards are correct for both versions, and QR codes are generated correctly, and I any vCard generated, I test with my phones (Android 12 and Android 13 right now), and Google Contacts app and Samsung Contacts both fully support it, and they properly import them, including non english characters, and all the fields, with only photo url ignored).
10. vCard format is specified here: https://www.rfc-editor.org/rfc/rfc6350 and my plugin generates VCF file based on that specification. How the apps that read VCF interpret the file, and how they are made to import VCF and what they are supporting is not relevant, and if the VCF is correct, my plugin can’t enforce how the unrelated apps are reading the VCF. As I said, the Android mobile apps for VCF are working great, and support almost everything vCard4 supports. If the iPhone doesn’t support vCard4, whatever app you use to generate vCard4, is not going to work on iPhone, it is not relevant for my plugin.

Your last complaint about show as text, is correct, and this is indeed a bug, I will fix this in next version to show the data as plain list, without coded labels.

Now, I know that my plugin generates correct VCF, but I accept that some bugs might be in the code, so the best way to see if there is a bug, is for you to show me exactly what data you entered in the widget, and I will replicate that, and see what happens, and what maybe get’s broken when VCF is generated.

I also plan a minor update soon that will include some fixes and updates, so if you can provide me with content to test, maybe I uncover some bugs that need to be fixed, and will include that too.

Best regards,
Milan