Open thiago28x opened 1 year ago
I think it's related to the baileys event emitter. During my test, the messaging-history.set
event itself don't have a name
or notify
value. Hence that's why it's empty on the result. But strangely the upsert
(or update
IIRC) one has!
Let me know if anyone has an idea about this
will investigate, thank you.
I have the same problem. Until yesterday, it worked for some people. But, I realize that today it doesn't work anymore, in any kind of test. Result only:
{ "data": [], "cursor": null }
A device that was already synchronized did not present problems and responds normally. A new device plugged in today is unresponsive.
I believe a "step before" the request is necessary, but I don't know which one.
I'm also waiting for a response from the Ookamiiixd.
If you get a response or a solution, please post it here.
Hello. Any news?
Still have no idea, even people in baileys repo seems to be get away with this
Hello!
(greatly loving this api, awesome job. Im forking the project to hopefully contribute on a variable webhook to forward incoming messages heheh)
Issue: was wondering why the field "name" in the GET request for the route http://hostname:3000/:sessionId/contacts
returns always an empty value? timestamp same thing.