Skip to content
This repository has been archived by the owner on Apr 23, 2024. It is now read-only.

"RPCError: 400: MESSAGE_ID_INVALID" when using Send To feature #456

Open
albertopasqualetto opened this issue Apr 7, 2023 · 0 comments
Open
Labels
bug Something isn't working

Comments

@albertopasqualetto
Copy link
Contributor

albertopasqualetto commented Apr 7, 2023

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

@albertopasqualetto albertopasqualetto added the bug Something isn't working label Apr 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant