Access token refresh is not handled automatically

[alexcoopper]

Hi, for some reason the calProvider doesn't automatically refresh the expired token.

I have configured the refresh url, and provided the initial access token.
It working well on page refresh.

But after an hour, when the token expired, then it doesn't refreshed automatically

[dosubot[bot]]

Automatic token refresh in CalProvider depends on a correctly implemented refreshUrl endpoint. This endpoint must be a GET route that accepts the Authorization: Bearer header and returns a new access token in the format { accessToken: "fresh access token" }. If this endpoint is missing or misconfigured, the refresh will fail and you'll see 401 errors after the token expires. On page refresh, things work because the token is revalidated, but for automatic refresh, the endpoint must be accessible and return the expected response format (source).

Recent development shows that the internal token refresh logic (getValidAccessToken()) is currently incomplete—it doesn't actually refresh expired tokens, just returns the existing one. This means automatic refresh may not be fully reliable yet and should be addressed before production use (source).

If you want to handle token refresh more robustly, the recommended approach is to use the useOAuthFlow hook, which manages the token lifecycle and provides callbacks for when a new token is obtained. However, this hook may not be available in the latest Cal Atoms package, so you may need to explore alternative methods or keep an eye on updates from the maintainers (source).

For now, double-check your refreshUrl implementation and response format, and be aware that full automatic refresh support may not be available until the refresh logic is completed in the SDK.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}