Open xbassols opened 3 years ago
creating numbers
Are you using virtual/voip numbers? I doubt whatsapp likes those
Virtual, yes but it sends the messages just fine until I use the API.
I think you have to sacrifice a new real number for the test :)
I got banned twice yesterday with a real number, maybe it's related to the first waiting message, it always happens when I talk to the recipient for the first time.
They can definitely detect that something is off. It could be related to the first key exchange.
I've tested with Baileys using this example as base and so far no bans at all.
It could be related to how it sends the message, trying to emulate the user input. I'll test sending it with this library copying the same method they use whenever I find time just to validate the theory.
I've also noticed that when you link the client to the app it shows as a chrome browser instead of a custom app but that could be just some settings.
@xbassols It could be nice if you can share how did you create the virtual numbers for testing purposes. My experience with "twilio" failed (although it was a few years ago)
Any VoIP service that allows SMS should work. Ex. Google Voice, Skype, Vonage, Twilio... I use a mix of those to develop.
As a counterpoint, so far we've only seen bans from virtual Twilio numbers on emulators but real numbers have been safe.
I been banned twice using regular phone numbers, but was an error from the bot, start sending a lote of message.
when you get banned does the device used to create the account also get blacklisted?
Have you tried to get JID using isonwhatsapp request. https://pkg.go.dev/go.mau.fi/whatsmeow@v0.0.0-20220324174258-88645e9f36a7/types#IsOnWhatsAppResponse https://pkg.go.dev/go.mau.fi/whatsmeow#Client.IsOnWhatsApp
As explained here, if at any given point WhatsApp judges whatever you're doing as harmful to their servers or their users, you'll get banned.
So expect any kind of retaliation from the platform to prevent suspicious behavior: blacklisting your public IP or a range of public IPs, information associated with your device or phone number, etc.
The best you can do is to rethink your business logic so that it's easier for the WhatsApp algorithm to realize whatever you're doing is not harmful according to their ToS.
If you speak for a business that wants to integrate WhatsApp into their workflow at scale, I highly suggest you read that explanation and get a WhatsApp Business API key instead.
I've been doing more tests, creating numbers, chatting via my phone, getting replies etc, etc...
But as soon as I try to send a message via the API the first message is sent as: waiting for this message this may take a while
And whenever I send another one it bans the number.
This time the IP I'm using is residential and the same one where the phone is at. (sending via the phone works just fine)
This are the logs I see when sending via the api:
I'm using the version go.mau.fi/whatsmeow v0.0.0-20211103085107-c2cda88e7160