Bloqueio whatsapp apos atualizar o baylei conforme chamado #2643
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
Research direction
Start by reviewing the report and referenced issue #2643, focusing on the Baylei update and the claimed five-day WhatsApp block. The issue provides no API version, logs, code location, or reproduction steps, so first establish whether the behavior is reproducible and what Evolution API component is involved before defining completion criteria.
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?
Depois que atualizei o Baylei no meu evolution api, meu cliente me enviou que houve um bloqueio no whats dele por 5 dias. O que fazer nesse caso?
Grato
What did you expect?
Depois que atualizei o Baylei no meu evolution api, meu cliente me enviou que houve um bloqueio no whats dele por 5 dias. O que fazer nesse caso?
Grato
What did you observe instead of what you expected?
Depois que atualizei o Baylei no meu evolution api, meu cliente me enviou que houve um bloqueio no whats dele por 5 dias. O que fazer nesse caso?
Grato
Screenshots/Videos
No response
Which version of the API are you using?
Depois que atualizei o Baylei no meu evolution api, meu cliente me enviou que houve um bloqueio no whats dele por 5 dias. O que fazer nesse caso?
Grato
What is your environment?
Windows
Other environment specifications
Depois que atualizei o Baylei no meu evolution api, meu cliente me enviou que houve um bloqueio no whats dele por 5 dias. O que fazer nesse caso?
Grato
If applicable, paste the log output
Depois que atualizei o Baylei no meu evolution api, meu cliente me enviou que houve um bloqueio no whats dele por 5 dias. O que fazer nesse caso?
Grato
Additional Notes
Depois que atualizei o Baylei no meu evolution api, meu cliente me enviou que houve um bloqueio no whats dele por 5 dias. O que fazer nesse caso?
Grato
- Dominant language
- TypeScript
- Stars
- 9.6k
- Forks
- 7.3k
- PR merge metrics
- No merged PRs in 30d
Contributor 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-api
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
evolution-foundation/evolution-api#2700 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
All issues in evolution-foundation/evolution-api
Similar issues
-
VerificationGate: ATTRIBUTION quote guard never matches a normal quotation (\b around the quote) Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2234 ·
-
T: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100