Skip to content

Unable to Send Messages to WhatsApp Groups Was This Issue Fixed? #1561

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
darkklin opened this issue Jun 7, 2025 · 3 comments
Open

Unable to Send Messages to WhatsApp Groups Was This Issue Fixed? #1561

darkklin opened this issue Jun 7, 2025 · 3 comments

Comments

@darkklin
Copy link

darkklin commented Jun 7, 2025

Hi,
I'm currently using the Docker image atendai/evolution-api:homolog, and I’m still unable to send messages to WhatsApp groups.

Has this issue been fixed? If so, which version tag includes the fix?

Thanks in advance!

@sergio-scardigno
Copy link

Estoy usando la version v2.2.3 y tiene el mismo problama.

@patrickmau
Copy link

Same problem here. running 2.2.3 via latest docker-compose image.

Apparently the issue with Baileys, take a look at this: #1497 (comment)

@yewkay
Copy link

yewkay commented Jun 16, 2025

Yes same problem here too, I tried to rebuild using new baileys but got errors

src/api/integrations/channel/whatsapp/whatsapp.baileys.service.ts(1910,38): error TS2339: Property 'offerCall' does not exist on type '{ logger: ILogger; getOrderDetails: (orderId: string, tokenBase64: string) => Promise<OrderDetails>; getCatalog: ({ jid, limit, cursor }: GetCatalogOptions) => Promise<...>; ... 97 more ...; sendWAMBuffer: (wamBuffer: Buffer<...>) => Promise<...>; }'.
src/api/integrations/channel/whatsapp/whatsapp.baileys.service.ts(1911,36): error TS2339: Property 'terminateCall' does not exist on type '{ logger: ILogger; getOrderDetails: (orderId: string, tokenBase64: string) => Promise<OrderDetails>; getCatalog: ({ jid, limit, cursor }: GetCatalogOptions) => Promise<...>; ... 97 more ...; sendWAMBuffer: (wamBuffer: Buffer<...>) => Promise<...>; }'.

I tried to update inside the docker container using npm update baileys@6.7.17 ,
npm list showed correct baileys version.
restarted the container and it didn't work :(

It's possible that the current evo api codes need updating for Baileys 6.7.17

Edit: additional info, I'm using chatwoot with Evo Api, I tested via chatwoot group chat. Receiving was fine, sending failed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants