I'm currently encountering an issue with Next.js while in strict mode. This problem arises from double renders. Specifically, when using useSession, if the token expires, the system attempts to refresh the same token twice.

This situation becomes problematic because, when the initial token is refreshed in response to a simultaneous request, it inadvertently triggers a user sign-out due to the RefreshTokenError that I've implemented.

Although the first request successfully passes and revokes the token—rendering it unusable—resulting in an "OK" status, the second request encounters failure. This happens because the new token isn't acquired in time, causing the same token to be sent to the backend again which leads to sign-out event.

Sample code: (jwt callback)

const jwt = jose.decodeJwt(token.user.accessToken);
const expirationTime = jwt.exp;
const currentTime = Math.floor(Date.now() / 1000);

if (expirationTime && currentTime > expirationTime) {
   const result = await refreshToken(token.user.refreshToken)
   return { 
      ...token,
      accessToken: result.accessToken,
      refreshToken: result.refreshToken
    }
}

return token;

Anonye have any suggestions on how I can appraoch solving this issue?