fix: fix jwt token not being updated on the server #83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this still isn't working. i give up. for now at least. i'm going to disable the refresh token logic in a separate pr until i have some motivation to give this another try.
the issue is: the token isn't being updated on the server pass. this causes the refresh token function to run infinitely after an hour since it's always reading the old, outdated token
nextauthjs/next-auth#9715
vercel/next.js#49442 (comment)