evolution-api icon indicating copy to clipboard operation
evolution-api copied to clipboard

[BUG] Warning when sending messages

Open chibancas opened this issue 1 month ago • 1 comments

📋 Bug Description

evolution api is amazing but since I started using it there's a warning next to each message that is sent through it. like in those pictures. look at the warning icon and the warning message says "this message wont dissappear from the chat. It's posible that the sender has a deprecated whatshapp version."

I used the atendai/evolution-api:v2.2.3 docker image in my docker compose and then I changed to evoapicloud/evolution-api:v2.3.6

Image Image

🔄 Steps to Reproduce

do compose up over this and send messesages normally, without the warning

services: postgres: image: postgres:15 container_name: evolution_postgres restart: always env_file: - .env ports: - "127.0.0.1:5432:5432" volumes: - postgres_data:/var/lib/postgresql/data networks: - n8n_evoapi

redis: image: redis:7 dns: - 8.8.8.8 - 1.1.1.1 container_name: evolution_redis restart: always ports: - "127.0.0.1:6379:6379" command: ["redis-server", "--requirepass", "${REDIS_PASSWORD}"] env_file: - .env networks: - n8n_evoapi

evolution-api: container_name: evolution_api image: evoapicloud/evolution-api:v2.3.6 restart: always ports: - "127.0.0.1:8090:8080" env_file: - .env depends_on: - postgres - redis volumes: - evolution_instances:/evolution/instances networks: - n8n_evoapi

networks: n8n_evoapi: external: true

volumes: postgres_data: evolution_instances:

✅ Expected Behavior

make those warnings dissappear

❌ Actual Behavior

showed in the pics before

🌍 Environment

  • OS: [Ubuntu 22.04.5 LTS]
  • Evolution API version: [2.3.6]
  • Database: [PostgreSQL15]
  • Connection type: [Baileys]
  • All inside a a docker compose
  • Docker version: Docker version 28.5.1, build e180ab8

📋 Logs


📝 Additional Context

No response

chibancas avatar Nov 27 '25 11:11 chibancas

Hello! In the file package.json update baileys version to "baileys": "v7.0.0-rc.9" -> build your image -> recreate your container -> is done!

eowoosh avatar Nov 27 '25 11:11 eowoosh

sorry for being so late! and thanks for your anser. I just tried it and it doesn't work on my acutal instance. I'm gonna try in a new docker container without volummes

chibancas avatar Dec 09 '25 12:12 chibancas