"RPCError: 400: MESSAGE_ID_INVALID" when using Send To feature
albertopasqualetto opened this issue · 0 comments
albertopasqualetto commented
Describe the bug
status: 400,
body: {
error: '400: MESSAGE_ID_INVALID (caused by messages.ForwardMessages)',
details: {
code: 400,
errorMessage: 'MESSAGE_ID_INVALID',
name: 'RPCError',
message: '400: MESSAGE_ID_INVALID (caused by messages.ForwardMessages)',
stack: 'RPCError: 400: MESSAGE_ID_INVALID (caused by messages.ForwardMessages)\n' +
' at RPCMessageToError (/apps/node_modules/telegram/errors/index.js:28:12)\n' +
' at MTProtoSender._handleRPCResult (/apps/node_modules/telegram/network/MTProtoSender.js:517:58)\n' +
' at MTProtoSender._processMessage (/apps/node_modules/telegram/network/MTProtoSender.js:442:15)\n' +
' at processTicksAndRejections (node:internal/process/task_queues:95:5)\n' +
' at MTProtoSender._recvLoop (/apps/node_modules/telegram/network/MTProtoSender.js:418:17)'
}
When trying to send file directly to username
I saw that it seems to not pass the id number to share api endpoint.
Expected behavior
Send file with no errors
Selfhosted