We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have read:
I am using the latest version of the library.
allowed_updates should be set when calling the setWebhookInfo function
setWebhookInfo
allowed_updates is not set when calling the setWebhookInfo function
getWebhookInfo
The text was updated successfully, but these errors were encountered:
I have the same problem, but I do through:
const allowed = ["chat_member", "message", "my_chat_member"];
export const bot = new TelegramApi( process.env.TG_KEY, { polling: { allowed_updates: allowed, } });
also try:
export const bot = new TelegramApi( process.env.TG_KEY, { polling: { params: { allowed_updates: allowed, } } });
At the same time, if I call just through the browser: https://api.telegram.org/botMY_TOKEN/getUpdates?allowed_updates=["chat_member", "message", "my_chat_member"]
and check by accessing /getWebhookInfo, I can see that the parameters were successfully set....
Sorry, something went wrong.
Update!
export const bot = new TelegramApi( process.env.TG_KEY, { polling: { params: { allowed_updates: JSON.stringify(allowed), } } });
JSON.stringify - fix this problem!
No branches or pull requests
I have read:
I am using the latest version of the library.
Expected Behavior
allowed_updates should be set when calling the
setWebhookInfo
functionActual Behavior
allowed_updates is not set when calling the
setWebhookInfo
functionSteps to reproduce the Behavior
setWebhookInfo
with custom allowed_updates fieldsgetWebhookInfo
and see that allowed_updates is not setsetWebhookInfo
with allowed_updates field in the bodygetWebhookInfo
and see that allowed_updates is correctly set.The text was updated successfully, but these errors were encountered: