Refreshed token doesn't contain capabilities for all channels

[sacOO7]

• Customer has reported an issue where refreshed token doesn't contain all channels, causing existing channels to reconnect again.

The current issue is that when Ably hits the token expiry time, it makes multiple token refresh calls. Although the current token has all the necessary capabilities, the server sometimes responds with a token containing only the channel_name provided in the payload. This causes the token to be marked as invalid, which then triggers another refresh cycle to obtain a token with proper capabilities.

• Link to internal conversation => https://ably-real-time.slack.com/archives/CURL4U2FP/p1733135454672739

┆Issue is synchronized with this Jira Bug by Unito

[sacOO7]

A temporary solution for now would be to set maximum ABLY_TOKEN_EXPIRY in .env file.

ABLY_TOKEN_EXPIRY= 86400  // 1 day ( 24 * 60 * 60 ) seconds

[sacOO7]

• Generally, ably requests the client to renew the token 30 seconds before expiry as per RTN22
• Link to internal conversation -> https://ably-real-time.slack.com/archives/C8SPU4589/p1724236742837859