-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Robot cannot receive reference message #3179
Comments
If the replied message isn't accessible to the bot, then it can't receive the message in private chats and basic groups. |
Yes, the message I quoted is from another robot. So, how can I upgrade to a super group more quickly? Are there any fixed metrics |
Only owner of the group can upgrade it. |
thanks |
Why
Great
…On Thu, 12 Dec 2024 at 04:55, hui87667137 ***@***.***> wrote:
thanks
—
Reply to this email directly, view it on GitHub
<#3179 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BLBYQ2KYZOLOMAANTDJW3LD2FECMFAVCNFSM6AAAAABTNO2NDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZXG42TMMJSGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am currently experiencing a problem where I am sending a reference message in a group chat, but the chatbot in the group chat does not receive the reply_to_maessage field in the callback content of the webhook
If it's a super group, this problem doesn't exist
Now I hope the robot can receive the reference content I sent. Is there any solution,
This is my current plan, transferring the group chat to another user will upgrade it to a super group, and then the robots in the super group can receive the reference content I send
Is there any other better solution?
If this is the only solution, how can I more conveniently upgrade to a super group? Because some groups are not owned by me, I cannot do the above operations
The text was updated successfully, but these errors were encountered: