Describe the bug
About 5 years ago, numbers in Brazil had the format 99 9999-9999.
Due to the increasing number of numbers, a ninth digit was added and became 99 9 9999-9999.
If I use the api to send a message to a number with the new digit and the account was initially registered without the ninth digit, the message is not delivered. I send an image to exemplify.
Note in the image that if I send it to the new number with the ninth digit, the message is not delivered.
This creates a difficulty, as everyone passes the number with the ninth digit, but when sending the message using the api, it is not delivered.
It's impossible to know if the number was registered in WA with or without the 9th digit and via the current API. The mobile app (and the web version as well) translates to the correct user id automatically.
Version
{
"version": "2023.12.1",
"engine": "WEBJS",
"tier": "CORE",
"browser": "/usr/bin/chromium"
}
To Reproduce Steps to reproduce the behavior:
- Just find someone with an old Brazilian account (you can use mine, sent on Patreon messages). I will love to receive test messages and will read & reply to confirm. Just send a text "testing WhatsApp"or smth and I will understand.
- Try to send a message to the number with the new digit.
- The message will not arrive
Expected behavior
The message should be sent. A workaround can be applied in the /api/contacts/check-exists endpoint that can return the user id
Screenshots

Additional context
Describe the bug
About 5 years ago, numbers in Brazil had the format 99 9999-9999.
Due to the increasing number of numbers, a ninth digit was added and became 99 9 9999-9999. If I use the api to send a message to a number with the new digit and the account was initially registered without the ninth digit, the message is not delivered. I send an image to exemplify.
Note in the image that if I send it to the new number with the ninth digit, the message is not delivered. This creates a difficulty, as everyone passes the number with the ninth digit, but when sending the message using the api, it is not delivered.
It's impossible to know if the number was registered in WA with or without the 9th digit and via the current API. The mobile app (and the web version as well) translates to the correct user id automatically.
Version
{ "version": "2023.12.1", "engine": "WEBJS", "tier": "CORE", "browser": "/usr/bin/chromium" }To Reproduce Steps to reproduce the behavior:
Expected behavior
The message should be sent. A workaround can be applied in the /api/contacts/check-exists endpoint that can return the user id
Screenshots

Additional context