-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
error in JSONRPC's get_message() #5370
Comments
Info messages have This looks more like an attempt to load trashed message, info messages should be loadable without problems and desktop does it all the time. |
This might be it, I started using more often "delete_device_after" in my bots to not keep private data that is not necessary, it might be that the messages are trashed by the time the bot already fetched the "next messages" IDs in some situations like bot start/resume |
@adbenitez Could you check with the updated core that logs msg_id which message it is? |
With #5464 it is not possible to load trashed messages anymore. |
My bots are sometimes getting an internal JSONRPC error when using API call get_message() it seems related to the "new" info messages shown when some peer changed keys and chat protection is broken, for some reason loading such messages with get_message() results in an exception when get_message() internally tries to load the sender contact (this special messages have no real sender) at least this is my assumption of the cause of the error
The text was updated successfully, but these errors were encountered: