What's the correct way to have the client automatically renew tokens?

[Zer0-One]

Client takes a client_secret in the constructor. How is this meant to be used to generate/refresh tokens?

[chillymosh]

For the token you pass in for the main Bot / Client to connect to IRC you need to validate / refresh that yourself on startup.
The token will remain working even if expired whilst connected to chat.

For API / Helix calls you can use the below event in your main bot subclass, this is obviously just a basic example as everyone has their own infrastructure to store tokens, refresh_tokens and so on.
That's the same use that passing the client_secret has in the bot constructor if it already knows the refresh token.

    async def event_token_expired(self):
        params = {
            "client_id": "",
            "client_secret": "",
            "grant_type": "refresh_token",
            "refresh_token": ""
        }
        async with aiohttp.ClientSession() as session:
            async with session.post("https://id.twitch.tv/oauth2/token", params=params) as response:
                token = await response.json()
                return token.get("access_token")

[Zer0-One]

I gave this a try, and I don't think that this event ever actually fires. I added a log line at the very beginning, and it never gets printed, and the code I added to update the tokens on disk never runs. I'm not sure what I'm doing wrong here.

For reference, this is what the log looks like when it begins to fail:

2023-07-23 03:49:34 DEBUG Dispatching event: raw_data
2023-07-23 03:49:34 DEBUG dispatching event raw_data
2023-07-23 03:49:34 DEBUG ACTION: Sending PONG reply.
2023-07-24 22:42:29 DEBUG  > PONG :tmi.twitch.tv
2023-07-24 22:42:30 DEBUG  < PING :tmi.twitch.tv

2023-07-24 22:42:30 DEBUG Dispatching event: raw_data
2023-07-24 22:42:30 DEBUG dispatching event raw_data
2023-07-24 22:42:30 DEBUG ACTION: Sending PONG reply.
2023-07-24 22:42:30 DEBUG  > PONG :tmi.twitch.tv
2023-07-24 22:42:30 ERROR Websocket connection was closed: None
2023-07-24 22:42:30 DEBUG  > PASS oauth:<REDACTED>
2023-07-24 22:42:30 DEBUG  > NICK <REDACTED>
2023-07-24 22:42:30 DEBUG  > CAP REQ :twitch.tv/commands
2023-07-24 22:42:30 DEBUG  > CAP REQ :twitch.tv/tags
2023-07-24 22:42:30 DEBUG  > CAP REQ :twitch.tv/membership
2023-07-24 22:42:30 DEBUG  > JOIN #<REDACTED>
2023-07-24 22:42:30 DEBUG  < :tmi.twitch.tv NOTICE * :Login authentication failed
:tmi.twitch.tv CAP * ACK :twitch.tv/commands

It then continues to attempt to reconnect indefinitely, despite the token being bad.

[chillymosh]

As I mentioned above, it's for Helix / API calls only, not the main chatbot token.
You need to handle refreshing that yourself for now in 2.x

[Zer0-One]

I'm confused about how to apply the new credentials to the Client. I don't see any methods for this. Are you supposed to disconnect the bot and spin up a new client every time you refresh the token?