-
Notifications
You must be signed in to change notification settings - Fork 66
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
Chat.deleteMessagesBulk() seems doesn't work #151
Comments
Will investigate and try to check whats going on. I'll keep you updated |
Okay, Thank you. I'll be looking foward to this issue. |
Hello, I've pushed the following commit: 1a9c1a4 Which introduces fixes for deleting messages, rewrote the message bulk deleting to be more accurate & added uuids. Could you try it and tell me how it goes? |
Hello, Sorry for the late response... Thank you for the fixes!.. i'll try it soon in about a few hours when I got into my computer, and give you how it will goes... |
Hello! Let me know. |
Hello, thank you for waiting... I tried to do it outside of my chatbot code and separate the code into this:
The
Any suggestions for this?... |
are you looking at the old or new interface? (chat/chat2, see url) |
After a bit of research, the website version does all the message deleted... I've been using the mobile version all the time to check it by the way... where it's kinda buggy... Sorry my bad... but i'm glad it's working now... Thank you for your patience in dealing with this issue!! 😀 |
No problem. Again the fact you've seen new changes is because its on the new ui, synced to the mobile one, using websockets. |
Hello there, i tried to delete a messages using
chat.deleteMessagesBulk()
but somehow it returns with no errors and on the website itself, the messages didn't get deletedHere is my code like (I recently making a chatbot using this package):
Maybe are there something wrong on my code? or it's from the package-side (I saw some old issue about
DeleteMessage
, Like issue #14) ?Any answers are appreciated, thank you.
The text was updated successfully, but these errors were encountered: