Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error getting user: { message: 'Invalid Refresh Token', status: 400 } #176

Closed
lumenwrites opened this issue Jul 13, 2022 · 3 comments
Closed

Comments

@lumenwrites
Copy link

Hi! I'm building a Next.js app using the help of this library.

From time to time I'm seeing the following error in my logs:

Error getting user: { message: 'Invalid Refresh Token', status: 400 }

I'm relatively new to supabase, I don't really understand why this is happening. I see this error from time to time in my local development logs, and in the logs of my app deployed on Vercel.

Can you help me figure out why this is happening, and what can I do to resolve it?

@silentworks
Copy link
Contributor

Has this been resolved now? also, it seems this isn't related to this repo but to your general supabase setup, am I correct in assuming this?

@codewriter73
Copy link

I'm also running into this error, although I'm just beginning to investigate this. For me, it can be reproduced by logging in using the basic

const { error } = await supabaseClient.auth.signIn({ email, password });

and then leaving the page open for around an hour, and when I hot reload it throws this error. Sometimes it's fixed by hard refreshing the page, while sometimes I have to sign out and sign back in. In my UserProvider I do have autoRefreshToken set to true. I'm not doing much else other than basic database calls, so I'm not quite sure what is causing this at the moment.

@silentworks
Copy link
Contributor

Duplicate of #171

@silentworks silentworks marked this as a duplicate of #171 Jul 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants