[Solved] ReferenceError: ctx is not defined

alexandershalin

I've set up this bot a week ago and it worked correctly. After updating to the latest version (where config.js was presented), I've got the following error message in logs when bot tries to redirect my message to a group:

Aug 17 13:28:47 support-bot node[759]: (node:759) UnhandledPromiseRejectionWarning: 
ReferenceError: ctx is not defined
Aug 17 13:28:47 support-bot node[759]:     at customerChat (/home/addappter/telegram-support-bot/bin/ticket_handler.js:43:22)
Aug 17 13:28:47 support-bot node[759]:     at /home/addappter/telegram-support-bot/bin/ticket_handler.js:11:13
Aug 17 13:28:47 support-bot node[759]:     at <anonymous>
Aug 17 13:28:47 support-bot node[759]:     at process._tickCallback (internal/process/next_tick.js:188:7)
Aug 17 13:28:47 support-bot node[759]: (node:759) 
UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which
Aug 17 13:28:47 support-bot node[759]: (node:759) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit c

bostrot

Welcome to the forum

I kinda messed the upload up earlier. I just pushed a new commit which adds the ctx and bot variables to the function. See this commit: https://github.com/bostrot/telegram-support-bot/commit/6f0517c8f95a2dcbfaa1bafd50b70d0c5c340d4c

If you agree I would also like to make a list of companies that uses the bot, if you want write the service you provide here 😉

Juliopp

Hey bostrot 🙂

Thanks for your fantastic job on this!

With the new commit, I still get "UnhandledPromiseRejectionWarning: ReferenceError: ctx is not defined" whenever the Staff group gets an answer (but it works fine forwarding messages from the user). Got any clue on why?

Thank you!

bostrot

Welcome to the Forum @Juliopp 😃
Thanks for mentioning that. I just pushed a new commit which should fix this too: https://github.com/bostrot/telegram-support-bot/commit/3076141805ff60211164acf5ed3ff833b5d4af78.

Kind regards,
Eric