Testei todos os botões/listas, retorna 200 mas nenhum chega (exceto carrossel)
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the behavior with evoapicloud/evolution-go:0.7.1 on Linux, comparing text messages with the buttons and lists shown in the screenshot. Inspect the send flow and available logs to determine why requests appear successful but messages do not arrive. Done means button and list messages reach the destination number while carousel delivery continues to work.
Written by the indexing model from the issue text.
Description
Welcome!
- Yes, I have searched for similar issues on GitHub and found none.
What did you do?
Mensagem de texto chega normalmente. De resto, nada funciona na tela do print abaixo.
What did you expect?
O esperado era que a mensagem chegasse no número de destino, mas nao chega
What did you observe instead of what you expected?
Nada acontece, embora tudo pareça ok no momento do envio, conforme print
Screenshots/Videos
No response
Which version are you using?
evoapicloud/evolution-go:0.7.1
What is your environment?
Linux
If applicable, paste the log output
No response
Additional Notes
No response
- Dominant language
- Go
- Stars
- 918
- Forks
- 488
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from evolution-foundation/evolution-go
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
evolution-foundation/evolution-go#193 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
evolution-foundation/evolution-go#104 ·
Maintainers usually reply within 5 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
evolution-foundation/evolution-go#101 ·
Maintainers usually reply within 5 days
-
POST /group/participant always returns 400 "participants is required and cannot be empty" (wrong validation middleware on route)Possibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
evolution-foundation/evolution-go#97 · 2 comments ·
Maintainers usually reply within 5 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
evolution-foundation/evolution-go#211 ·
Maintainers usually reply within 5 days
All issues in evolution-foundation/evolution-go
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
txn2/mcp-data-platform#2030 ·
Maintainers usually reply within 1 day
-
area/tests theme/ci-dx
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
ai-inspected
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
[Bug]: e2e script flag parsing is brokenPossibly taken @ericcurtin claimed this today. Openarea/dev-infra area/tests kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
agent-substrate/substrate#2217 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug]: multi-arch `vgpu-device-manager` image digest not pinned in OLM bundlePossibly taken @MrBeldum claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NVIDIA/gpu-operator#3012 · 1 comment ·
Maintainers usually reply within 1 day