Welcome!
What did you do?
I sent an outgoing message through Evolution API v2.3.7 using the official Docker image.
The API accepted the request and returned the message with the PENDING status, but the recipient did not receive it.
The WhatsApp account was working normally because messages sent directly from the WhatsApp Business app were delivered without any problem.
Before changing the Baileys version, I tested the following:
Created a new Evolution instance.
Disconnected and paired the WhatsApp account again.
Tested without proxy.
Enabled Redis and confirmed that the connection and session cache were working.
Confirmed that the instance status was open and connected.
The issue continued after all these tests.
I checked the Baileys version inside the official image and confirmed that it was 7.0.0-rc.9.
As a workaround, I created a custom Docker image based on Evolution API v2.3.7 and updated only Baileys to 7.0.0-rc13.
After recreating the Evolution API container with this custom image, outgoing messages started being delivered normally.
What did you expect?
I expected messages accepted by the API to be delivered to the recipient and to progress normally from the PENDING status.
The official Docker image should use a Baileys version that allows outgoing messages to be delivered correctly.
In the same environment, updating Baileys from 7.0.0-rc.9 to 7.0.0-rc13 fixed the issue.
What did you observe instead of what you expected?
With Baileys 7.0.0-rc.9, the API accepted the outgoing message and returned the PENDING status, but the recipient did not receive the message.
The instance remained open and connected, and messages sent directly from the WhatsApp Business app worked normally.
After updating only Baileys to 7.0.0-rc13, the same Evolution API installation started delivering messages normally.
Screenshots/Videos
No response
Which version of the API are you using?
2.3.7
What is your environment?
Linux
Other environment specifications
VPS running Linux
Docker and Docker Compose
Official image: evoapicloud/evolution-api:latest
PostgreSQL
Redis enabled
WhatsApp provider: Baileys
No proxy configured
Baileys version in the official image: 7.0.0-rc.9
Baileys version in the working custom image: 7.0.0-rc13
If applicable, paste the log output
No response
Additional Notes
The current official Docker image still contains Baileys 7.0.0-rc.9.
I created a custom image based on evoapicloud/evolution-api:v2.3.7 and changed only the Baileys dependency to 7.0.0-rc13.
After recreating the API container with the custom image, outgoing messages started being delivered normally.
The develop branch already appears to use Baileys 7.0.0-rc13, but the official latest Docker image is still using rc.9.
Could a new official Docker image be published with Baileys 7.0.0-rc13?
Welcome!
What did you do?
I sent an outgoing message through Evolution API v2.3.7 using the official Docker image.
The API accepted the request and returned the message with the PENDING status, but the recipient did not receive it.
The WhatsApp account was working normally because messages sent directly from the WhatsApp Business app were delivered without any problem.
Before changing the Baileys version, I tested the following:
Created a new Evolution instance.
Disconnected and paired the WhatsApp account again.
Tested without proxy.
Enabled Redis and confirmed that the connection and session cache were working.
Confirmed that the instance status was open and connected.
The issue continued after all these tests.
I checked the Baileys version inside the official image and confirmed that it was 7.0.0-rc.9.
As a workaround, I created a custom Docker image based on Evolution API v2.3.7 and updated only Baileys to 7.0.0-rc13.
After recreating the Evolution API container with this custom image, outgoing messages started being delivered normally.
What did you expect?
I expected messages accepted by the API to be delivered to the recipient and to progress normally from the PENDING status.
The official Docker image should use a Baileys version that allows outgoing messages to be delivered correctly.
In the same environment, updating Baileys from 7.0.0-rc.9 to 7.0.0-rc13 fixed the issue.
What did you observe instead of what you expected?
With Baileys 7.0.0-rc.9, the API accepted the outgoing message and returned the PENDING status, but the recipient did not receive the message.
The instance remained open and connected, and messages sent directly from the WhatsApp Business app worked normally.
After updating only Baileys to 7.0.0-rc13, the same Evolution API installation started delivering messages normally.
Screenshots/Videos
No response
Which version of the API are you using?
2.3.7
What is your environment?
Linux
Other environment specifications
VPS running Linux
Docker and Docker Compose
Official image: evoapicloud/evolution-api:latest
PostgreSQL
Redis enabled
WhatsApp provider: Baileys
No proxy configured
Baileys version in the official image: 7.0.0-rc.9
Baileys version in the working custom image: 7.0.0-rc13
If applicable, paste the log output
No response
Additional Notes
The current official Docker image still contains Baileys 7.0.0-rc.9.
I created a custom image based on evoapicloud/evolution-api:v2.3.7 and changed only the Baileys dependency to 7.0.0-rc13.
After recreating the API container with the custom image, outgoing messages started being delivered normally.
The develop branch already appears to use Baileys 7.0.0-rc13, but the official latest Docker image is still using rc.9.
Could a new official Docker image be published with Baileys 7.0.0-rc13?