Open Chist-Sergey opened 2 months ago
Temporary fixed by removing every non-group chat id from database.
It's far worse than that. The bot is not starting at all, even if it tells you so. For now, it's best to use a stable release.
Logs say dat the 'birthday_start' function tries to open a chat with a wrong file name.
It should open a 12345.txt
file, but tries to open a 12345.txt.txt
file.
This case is under investigation.
Status: reproducing.
Had not encountered this error for a while now. Let's see how it would behave at production server.
It doesn't happen in a testing enviroment.
Somehow it's raised during the message part, but I think it's the misleading part. It should NOT send message to a user who has the bot blocked. It SUPPOSED to send a message to a user who have initialised the bot by the "start" command, which also unblocks the bot if it were ever previously blocked. Should I try to except this error?