Skip to content
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 400 MESSAGE_IDS_EMPTY - supergroup topic - reply_media_group & reply_video #101

Open
3 tasks done
ndyanx opened this issue Nov 23, 2024 · 0 comments
Open
3 tasks done

Comments

@ndyanx
Copy link

ndyanx commented Nov 23, 2024

Checklist

  • I am sure the error is coming from Pyrofork's code and not elsewhere
  • I have searched in the issue tracker for similar bug reports, including closed ones
  • I ran pip3 install -U git+https://github.com/Mayuri-Chan/pyrofork and reproduced the issue using the latest development version

Description

Description: When attempting to send a (reply_media_group or reply_video) to a topic within a supergroup, Does not get sent directly to the topic. Instead, it gets placed in the scheduled messages of the topic.
I'm using a userbot premium

Steps to reproduce

1.reply_media_group or reply_video

Code example

No response

Logs

File "C:\Users\randy\Desktop\testbot\testbot\manager\_message.py", line 93, in reply_media_group
    msgs_list = await message.reply_media_group(
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\randy\Desktop\testbot\.venv\Lib\site-packages\pyrogram\types\messages_and_media\message.py", line 2837, in reply_media_group
    return await self._client.send_media_group(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\randy\Desktop\testbot\.venv\Lib\site-packages\pyrogram\methods\messages\send_media_group.py", line 497, in send_media_group
    return await utils.parse_messages(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\randy\Desktop\testbot\.venv\Lib\site-packages\pyrogram\utils.py", line 151, in parse_messages
    reply_messages = await client.get_messages(
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\randy\Desktop\testbot\.venv\Lib\site-packages\pyrogram\methods\messages\get_messages.py", line 117, in get_messages
    r = await self.invoke(rpc, sleep_threshold=-1)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\randy\Desktop\testbot\.venv\Lib\site-packages\pyrogram\methods\advanced\invoke.py", line 80, in invoke
    r = await self.session.invoke(
        ^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\randy\Desktop\testbot\.venv\Lib\site-packages\pyrogram\session\session.py", line 420, in invoke
    return await self.send(query, timeout=timeout)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\randy\Desktop\testbot\.venv\Lib\site-packages\pyrogram\session\session.py", line 377, in send
    RPCError.raise_it(result, type(data))
File "C:\Users\randy\Desktop\testbot\.venv\Lib\site-packages\pyrogram\errors\rpc_error.py", line 93, in raise_it
    raise getattr(
pyrogram.errors.exceptions.bad_request_400.MessageIdsEmpty: Telegram says: [400 MESSAGE_IDS_EMPTY] (caused by "channels.GetMessages") Pyrogram 2.3.50 thinks: The requested message doesn't exist or you provided no message id
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant