Skip to content

arbitrary_callback_data tries to match some UUID to the CallbackQueryHandler's pattern #3122

Answered by Poolitzer
AusiasMarch asked this question in Q&A
Discussion options

You must be logged in to vote

The actual issue though, if I see it correctly, that you use Updater() without setting arbitrary_callback_data to True or passing your created bot instance, thus the dispatcher/updater cant resolve the arbitrary_callback_data passed by the other ExtBot instance properly and you receive the uuid in your filter instead of the long x string you expect.

Replies: 3 comments 5 replies

Comment options

You must be logged in to vote
1 reply
@AusiasMarch
Comment options

Comment options

You must be logged in to vote
1 reply
@Bibo-Joshi
Comment options

Answer selected by AusiasMarch
Comment options

You must be logged in to vote
3 replies
@Poolitzer
Comment options

@AusiasMarch
Comment options

@Poolitzer
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants