Closed bostrot closed 2 years ago
Commit af43951c5ff80831b9ce2681b7d7e6b35417a8f4 should improve error handling with catching the reply function. Still needs to be tested if it actually solves it as the error is hard to reproduce.
Closing for now as that commit should have fixed it for now. Reopen if that error reoccurs.
Hey @bostrot I'm getting an error adding bot to supergroup, are there any workaround to fix it?
Thu Jun 23 2022 06:31:19 GMT+0000 (Coordinated Universal Time): Error: 400: Bad Request: group chat was upgraded to a supergroup chat
Hey @bostrot I'm getting an error adding bot to supergroup, are there any workaround to fix it?
Thu Jun 23 2022 06:31:19 GMT+0000 (Coordinated Universal Time): Error: 400: Bad Request: group chat was upgraded to a supergroup chat
Yes, see following: https://github.com/bostrot/telegram-support-bot/issues/16#issuecomment-491625213
@bostrot thank you. Updated settings in bot father (for the group), also gave it admin privileges in group (even they are not required).
Bot continues to reply: Message is not sent due to an error.
And the logs like this:
'Mon Jul 18 2022 10:05:20 GMT+0000 (Coordinated Universal Time): Error: 400: Bad Request: chat not found\n' +
p.s. Working fine while not in supergroup.
@bostrot thank you. Updated settings in bot father (for the group), also gave it admin privileges in group (even they are not required).
Bot continues to reply:
Message is not sent due to an error.
And the logs like this:
'Mon Jul 18 2022 10:05:20 GMT+0000 (Coordinated Universal Time): Error: 400: Bad Request: chat not found\n' +
p.s. Working fine while not in supergroup.
Please recheck your Group ID with the /id command.
@bostrot oh yeah, it works. We took id from web version of telegram before that. Thank you for that 🙏
Describe the bug Simliar to #65 unhandled rejections occur when the bot was kicked from a supergroup while trying to reply to a message.
Additional context