Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cant send vcard #2012

Closed
1 task done
NekoVer opened this issue Feb 19, 2023 · 4 comments
Closed
1 task done

cant send vcard #2012

NekoVer opened this issue Feb 19, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@NekoVer
Copy link

NekoVer commented Feb 19, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

Screenshot 2023-02-20 062452

Expected behavior

can use vcard

Steps to Reproduce the Bug or Issue

just send List as example script

Relevant Code

              console.log(client.info.wid)
            const vcard = "BEGIN:VCARD\n"
            + "VERSION:3.0\n"
            + "FN::******\n"
            + "TEL;type=CELL;type=VOICE;waid=:******:+:******\n"
            + "ORG:******\n"
            + "END:VCARD";
            client.sendMessage(vcard, MessageTypes.CONTACT_CARD, { parseVCards:true })

This My code

Browser Type

Chromium

WhatsApp Account Type

Standard

Does your WhatsApp account have multidevice enabled?

Yes, I am using Multi Device

Environment

Windows
Android
whatsapp-web.js - on the latest github commit
latest nodejs version (v18.14.0)

Additional context

No response

@NekoVer NekoVer added the bug Something isn't working label Feb 19, 2023
@tofers
Copy link
Contributor

tofers commented Feb 19, 2023

#1995

The problem is not new, there is already a solution. Expect a merger

@NekoVer
Copy link
Author

NekoVer commented Feb 19, 2023

#1995

The problem is not new, there is already a solution. Expect a merger

thx

@NekoVer NekoVer closed this as completed Feb 19, 2023
@NekoVer NekoVer reopened this Feb 19, 2023
@NekoVer
Copy link
Author

NekoVer commented Feb 19, 2023

#1995

The problem is not new, there is already a solution. Expect a merger

the solution didn't work for me

@NekoVer
Copy link
Author

NekoVer commented Feb 19, 2023

#1995

The problem is not new, there is already a solution. Expect a merger

@NekoVer NekoVer closed this as completed Feb 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants