search

mast / telegram-bot-api

First Telegram Bot API node.js library
http://mast.github.io/telegram-bot-api/
MIT License
246 stars 64 forks source link

Sudden error after getUpdates #41

Closed Alcotana closed 4 years ago

Alcotana commented 7 years ago

screenshot_134

What has happened? I cannot start the server, because of the error.

As far as I remember, I did npm update telegram-bot-api just before.

Is this the problem of telegram-bot-api?

fluse commented 7 years ago

i get this error too.

mast commented 7 years ago

I checked my test script for getUpdates and it works for me. Could you please locate place in your code where this happens and share it?

fluse commented 7 years ago

Hey mast.

.on('inline.callback.query' will fire .on('message' too

so you get inside on('message an different object where message.chat.id is not under the same dot notation.

and if you create an error inside message will throw this promise error

mast commented 7 years ago

and if you create an error inside message will throw this promise error

not sure I get you here..

Is the following true?

Due to wrong chat.id extraction, you send message to wrong chat (with empty chat_id probably), that's why you receive HTTP 400 back from Telegram servers? It sounds like bug in your code then.

mast commented 4 years ago

Closing issue as not reproducible