You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
A workaround can be applied in the /api/contacts/check-exists endpoint that can return the user id
I love the suggested workaround, the fix is available in 2023.12.2 PLUS version (will be available in CORE in the next release).
Checked it with provided phone number - it does add remove one 9 from the phone number.
GET /api/contacts/check-exists?phone=11231231231&session=default
You should use the GET /api/contacts/check-exists endpoint before sending a message to a new phone number
to get the correct chatId because of the additional 9-digit number added after 2012.
It's fine to send the response to chatId for incoming messages, though - the payload already has the correct chatId.
<off-topic>
About a year ago I wished to have detailed issues in the repo... My dream came true, it's a New Year gift! 😆 #27 (comment)
Thank you @arielpts for the such detailed issue, it's pleasure to see and fix that - you've done all work yourself, so it's safe to assume you've fixed the issue 👍
Obrigado! </off-topic>
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
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
The text was updated successfully, but these errors were encountered: