Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Log spam on getUpdates when BOT token is wrong / revoked

See original GitHub issue

Hello, with the latest version (4.3.0) i’m experiencing loops caused by wrong tokens on my BOTS. I have a BOT where users can configure their own BOT, so they enter their own token, and if they revoke the token I start getting a huge spam in logs:

INFO: Update listener error for request {"method":"getUpdates"} with response 401 Unauthorized
Jun 13, 2019 8:41:56 PM okhttp3.internal.platform.Platform log
INFO: Update listener error for request {"method":"getUpdates"} with response 401 Unauthorized
Jun 13, 2019 8:41:56 PM okhttp3.internal.platform.Platform log
INFO: Update listener error for request {"method":"getUpdates"} with response 401 Unauthorized
Jun 13, 2019 8:41:57 PM okhttp3.internal.platform.Platform log
INFO: Update listener error for request {"method":"getUpdates"} with response 401 Unauthorized

As you can see I get about 4 per second, so it’s like it’s looping. Is there any way to intercept this and kill the update listener?

Thanks a lot!

Issue Analytics

State:
Created 4 years ago
Comments:13 (6 by maintainers)

Top GitHub Comments

1reaction

pengradcommented, Jun 19, 2019

Released in 4.3.1 New usage is:

bot.setUpdatesListener(updates -> {
    // process updates
    return UpdatesListener.CONFIRMED_UPDATES_ALL;
}, e -> {
    if (e.response() != null) {
        // god bad response from telegram 
        e.response().errorCode();
        e.response().description();
    } else {
        // probably network error
        e.printStackTrace();
    }
});

0reactions

mircoianesecommented, Jul 7, 2019

No, I’m on 4.3.1. Shall I update?