-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
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
the library started failing (new update types) #237
Comments
in my case, the new events were causing failures. I added new enum variants like https://github.com/telegram-rs/telegram-bot/pull/221/files to my fork. It solved the issue |
TLDR; I added these updates to my fork as well. My fork has the fixes from Master. Not sure if it's worth a pull-request. master...mann-ed:master I created this my fork over a year ago to get inline response working, And i was just starting out learning RUST, so that is why there are several commits with same statement. I finally got it to work and went on to other things. Just recently my bot broke, and this is the fix. |
Using |
I wrote a new telegram library for rust - https://github.com/ayrat555/frankenstein. It's easy to use and have a minimal number of dependencies. You can even use an HTTP client of your choice |
Today the library started failing with :
I think it's happening because telegram added two new update types (https://core.telegram.org/bots/api-changelog#march-9-2021)
The text was updated successfully, but these errors were encountered: