QR Code Generator vCard Issue

cavanhorn1 wrote:

Thank you. It's a website. Their support isn't very helpful. If you don't find an answer to your question there isn't anywhere to send it.

Nobody here can assist with a (broken?) website QR code generator. Help with writing an app that provides a QR code generator, maybe. (I was looking at creating an app to do that a while back, so probably have more pointers I can dig up.)

Here’s a free app:

… https://apps.apple.com/us/app/qr-code-vcard/id1036132578

There are others.

More info on doing this:

… https://www.howtogeek.com/331698/how-to-make-your-own-qr-codes-from-your-iphone-or-android-phone/

Here’s an introduction to the vCARD format, so that you can look at the differences with what works and what doesn’t:

… https://www.evenx.com/vcard-3-0-format-specification

Here’s an example of using and troubleshooting the necessary format:

… https://stackoverflow.com/questions/14414796/qr-code-for-vcard-prepared-in-iphone-not-recognised-by-android-device

Here’s the vCARD format RFC:

… https://www.rfc-editor.org/rfc/rfc2426

I’d expect that more than a few “free” websites offering QR code vCARD generation services are primarily interested in collecting that info for spam. If the website you have been using was doing that, then they probably already got what they needed.

Check for updates, then contact the app vendor support.

cavanhorn1 wrote:

Thank you, but I don't think the website is broken. It works fine with my Samsung, it just doesn't with iPhone. iPhone reads the information, but doesn't specify the number title. The website specifies them when I enter the information and the Samsung reads it, but not the iPhone. This sounds like an iPhone issue to me. Is it a setting in iPhone? Is it an app? Not sure.

Different implementations can have different requirements and different extensions, can have different things that they’ll tolerate (and ignore), and each can have different bugs.

Whether this is an Android extension or an iPhone limit or bug or a website issue is unclear.

Which is why poking at the working and non-working vCARD strings will be involved, and checking the vCARD RFC and maybe related RFCs.

Stuff required in the RFC should work. Past that, it’s all optional, and use of a compatible subset is necessary, absent fixes or enhancements from the vendor(s) involved.