Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Calling getKindeServerSession() in @kinde-oss/kinde-auth-nextjs 2.3.7 threw a 500 error (e.g. when checking isAuthenticated in a navbar for a logged-out user). After login everything worked; the error only appeared with no active session. Seen on Next 15.1.4 / React 19.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Fixed in the 2.5 release of @kinde-oss/kinde-auth-nextjs; upgrade to 2.5 or newer. The maintainers confirmed the fix and it was in pre-release as 2.5.0-13 before the final. If you render auth-dependent UI like navbars, the fixed version handles the no-session case instead of throwing. Source: https://github.com/kinde-oss/kinde-auth-nextjs/issues/204
Fixes getKindeServerSession() throwing a 500 in @kinde-oss/kinde-auth-nextjs 2.3.7 when there is no active session.
Shows how to fix exchange refresh token for access token returns HTTP 500 (fixed in 1.49.0). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes 15Five API error engagement export returns 500 on large date range in 15Five API by applying the specific fix in the steps and proving it on one survey, team or department first.