sendText for a group, it is returning error "The number does not exist". (the same number and the same code worked a month ago)
See original GitHub issueDescription
sendText for a group, it is returning error “The number does not exist”.
ps1: the same number and the same code worked a month ago! ps2: works for some other numbers! ps3: for security, the group number has been modified here
thanks!
Environment
Venom: 4.3.0 Node: v16.14.0
Steps to Reproduce
Just run the code below
Log Output
{
"me": {},
"to": "550000000000-1500000000@g.us",
"erro": true,
"text": "The number does not exist",
"status": 404,
"result": null
}
Code
await venomClient.sendText('550000000000-1500000000@g.us', 'TEST! PING..');
Issue Analytics
- State:
- Created a year ago
- Comments:13
Top Results From Across the Web
Error Invalid Number message in texts. - Apple Community
I thought I fixed this problem a month ago per another discussion's suggestions. I had been getting the "+1(1)216116-11 Error Invalid Number ......
Read more >google chrome extension - Port error: Could not establish ...
Using the new api sendMessage/onMessage to send messages instead of sendRequest/onRequest i'm getting the following error in the JS console : Port error:...
Read more >Error Messages | Help - Zoho Deluge
This error message will be displayed if a function that does not return any value is assigned to a variable, or used as...
Read more >Sending Messages | Twilio
If you attempt to send an SMS from your trial account to an unverified number, the API will return Error 21219. You can...
Read more >Amazon SQS visibility timeout - Amazon Simple Queue Service
Because Amazon SQS is a distributed system, there's no guarantee that the consumer ... group ID, no more messages for the same message...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Dear, as there is no answer, I advise you to migrate to whatsapp-web.js, I have already tested it and it works well. and I’m already migrating.
Facing same problem on 4.3.6