How to disable supabase ssr logs
Supabase getClaims error: Invalid Refresh Token: Refresh Token Not Found
AuthApiError: Invalid Refresh Token: Refresh Token Not Found
at dk (.next/server/src/middleware.js:33:29611)
at async dm (.next/server/src/middleware.js:33:30585)
at async dl (.next/server/src/middleware.js:33:29995)
at async c (.next/server/src/middleware.js:33:66145)
at async (.next/server/src/middleware.js:33:66408) {
isAuthError: true,
status: 400,
code: 'refresh_token_not_found'
}
AuthApiError: Invalid Refresh Token: Refresh Token Not Found
at dk (.next/server/src/middleware.js:33:29611)
at async dm (.next/server/src/middleware.js:33:30585)
at async dl (.next/server/src/middleware.js:33:29995)
at async c (.next/server/src/middleware.js:33:66145)
at async (.next/server/src/middleware.js:33:66408) {
isAuthError: true,
status: 400,
code: 'refresh_token_not_found'
}
Supabase getClaims error: Invalid Refresh Token: Refresh Token Not Found
How to catch and handle these logs? are they internally loged? too many logs are causing my server to go out of disk space!
3 Replies
You cannot catch them, they have a wrapper function which doesn't allow for catching of these anymore. You could in earlier 2.x versions of the library but they changed this to fix a edge case.
If this error is logging that much, it seems like you have an issue in your code.
Refresh token not found, its not from my code
Its normal that these errors are logged?
These error appear when a token is expired which happens to every user