Next.js SSR: intermittent JWT token expired errors

Intermittent 'JWT token expired' errors in Next.js SSR (both client and server, with getNhostSession) were an SDK bug in the token refresh path, already fixed upstream. Upgrade your Nhost JS SDKs (@nhost/nextjs, @nhost/react) to the release containing the fix. If you're pinned to an old version and see random auth expiry under SSR, update first before debugging your session code.

Source: gh:nhost/nhost#2348 (Nhost)

In gh:nhost/nhost#2348, the issue was: I'm investigating integrating next + nhost with SSR enabled (pages router). Setup: [NhostProvider] + [NhostApolloProvider] + getNhostSession from nhost/nextjs. In general it works really well. But sometimes (and it's not clear when and why) I receive errors about JWT token being expired, both on client and server.. The verified answer: Intermittent 'JWT token expired' errors in Next.js SSR (both client and server, with getNhostSession) were an SDK bug in the token refresh path, already fixed upstream. Upgrade your Nhost JS SDKs (@nhost/nextjs, @nhost/react) to the release containing the fix. If you're pinned to an old version and see random auth expiry under SSR, update first before debugging your session code.. Issue URL: https://github.com/nhost/nhost/issues/2348