Bot sends old, incorrect data on successful purchase. about grammy HOT 6 CLOSED

Got it working by moving all of the handlers to my createBot function within the index.ts file (which runs prior to the bot start) and the :successful_payment to its own function. It's quite messy but it works like expected. Big thanks for the help!

/**
 * Answers the checkout query which is required to continue with the payment.
 * @see https://core.telegram.org/bots/api#answerprecheckoutquery
 */
protectedInstance.on('pre_checkout_query', async (ctx) => ctx.answerPreCheckoutQuery(true));

/**
 * Responds to a successful payment and updates the user's balance.
 */
protectedInstance.on(':successful_payment', async (ctx) => processSuccessfulPayment(ctx, getProductInfo(getUpdateInfo(ctx).message?.successful_payment!.invoice_payload as AvailableProducts)!));

from grammy.

Thanks for the suggestion, I believe i'm already doing this with most of my modules but i'll check out the docs to make sure.

from grammy.

I am not sure that this will fix all of your code, but there is one mistake that stands out: you register further handlers on your composer inside an existing handler by calling composer.on a few times. This means that you alter the behaviour of your entire bot whenever an update is handled. Basically, whenever you run the code above, a new handler is added, so if you handle 5000 payments, then your bot now has 5000 handlers for ':successful_payment'. That surely is not what you meant, is it?

from grammy.

Yeah, that is definitely not the intended behaviour. Is there a way to see which handlers are added so I can perhaps try and see what's going on? Or do they not provide any useful information?

from grammy.

There is no way to see this, but in general, you should never add more handlers after your bot has started. You may want to use something like https://grammy.dev/plugins/conversations for this.

from grammy.

You can improve your code structure by defining things in modules, but registering things centrally. That is better than passing around composer instances to register middleware in many places. https://grammy.dev/advanced/structuring elaborates on this.

from grammy.