search

GochoMugo / tgfancy

A Fancy, Higher-Level Wrapper for Telegram Bot API
MIT License
184 stars 16 forks source link

forwardMessage not working after Bot API 3.4 release #18

Open zakeri opened 6 years ago

zakeri commented 6 years ago

I observed that after new bot API 3.4 release this code gives exception:

msg = await bot.forwardMessage(my_channel1_id, my_channel2_id, my_message_id);

Error: ETELEGRAM: 400 Bad Request: message to forward not found at request.then.resp (/home/hassan/telegram-ads/node_bot/node_modules/node-telegram-bot-api/src/telegram.js:213:15) at tryCatcher (/home/hassan/telegram-ads/node_bot/node_modules/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/home/hassan/telegram-ads/node_bot/node_modules/bluebird/js/release/promise.js:512:31) at Promise._settlePromise (/home/hassan/telegram-ads/node_bot/node_modules/bluebird/js/release/promise.js:569:18) at Promise._settlePromise0 (/home/hassan/telegram-ads/node_bot/node_modules/bluebird/js/release/promise.js:614:10) at Promise._settlePromises (/home/hassan/telegram-ads/node_bot/node_modules/bluebird/js/release/promise.js:693:18) at Async._drainQueue (/home/hassan/telegram-ads/node_bot/node_modules/bluebird/js/release/async.js:133:16) at Async._drainQueues (/home/hassan/telegram-ads/node_bot/node_modules/bluebird/js/release/async.js:143:10) at Immediate.Async.drainQueues (/home/hassan/telegram-ads/node_bot/node_modules/bluebird/js/release/async.js:17:14) at runCallback (timers.js:800:20) at tryOnImmediate (timers.js:762:5) at processImmediate [as _immediateCallback] (timers.js:733:5)

Any clue on why I am seeing this is appreciated.