RTN15h: token errors don't cause a connection to fail

[paddybyers]

RTN15h says:

if the token is renewable, a single attempt to create a new token should be made and a new connection attempt initiated using the new token. If the token creation fails, the next connection attempt fails due to a token error, or the token was not renewable, the connection will transition to the FAILED state ...

It think it is not correct that the connection fails in the case that the token is renewable; this is also inconsistent with RTN14b.

I think this needs to cover two cases separately:

• if the token is not renewable, then the connection transitions to FAILED;

• if the token is renewable, then the client immediately attempts to obtain a new token and reconnect; if that attempt fails (either the token renewal fails with a recoverable error, or the connection attempt fails with a token error) then the connection transitions to DISCONNECTED and may retry after the appropriate retry period.

┆Issue is synchronized with this Jira Task by Unito

[sync-by-unito]

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-2812