-
Notifications
You must be signed in to change notification settings - Fork 373
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
I'm getting a "Database error finding user" on signup using Supabase Auth #1061
Comments
There might be more specific information in the dashboard Postgres log right after the error. |
Also any chance you use the Prisma multiSchema feature? (I don't know what that is exactly) but at least one other user had their grants on the auth schema messed up by using that. |
Hey Gary - all my triggers have been disabled. I am using the Prisma multiSchema feature. I have tried restoring grants using this: https://supabase.com/docs/guides/integrations/prisma#missing-grants But the error still occurs. I can't even get the project usage statistics to show up... |
All I know is a discord user lost his auth grants using Prisma mulitSchema. The user never said what he did after, but I think started a new instance. The schema fix shown does not include auth schema I don’t believe. I suspect this is something new with Prisma/Supabase based on two of you in a week having it and not seeing this before. |
I also get this error : Describe the bug
this call give me :
every thing work fine on the second and all other call |
Same here, the lack of documentation and issues ive been facing with local Supabase development (using Prisma and the Supabase client) definitely has me reconsidering my decision to use Supabase as a BaaS for our startup. Hopefully we can resolve work to resolve this issue soon as I was looking forward to using Supabase. |
For me I resolved the issue by running |
this was a supabase key missing for me, check your env and auth token and add --debug to see if any other error can occur |
hello everyone, you can take a look at the detailed error returned from the logs explorer on the dashboard: https://app.supabase.com/project/_/logs/explorer and reach out to us at support (https://app.supabase.com/support/new) if you see something strange. |
Hey @christopheragnus, @marc-tech, @estebangarcia21, i'm not really familiar with prisma's multi schema feature, but it would be great you guys can suggest possible remediation steps or solutions that worked for you. If Prisma makes modifications to the auth schema under the hood, it will cause gotrue to fail since the auth schema is supposed to be managed by gotrue only. I'll be closing this issue since it's not related to gotrue but feel free to reopen it or comment in this thread. |
Same here, Prisma has been nothing but problems and pain for me, i'm about to ditch it. |
Bug report
Describe the bug
When I try to create a new user using the Auth components by Supabase. My code.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Network logs shows:
Expected behavior
New user should be created.
Screenshots
https://imgur.com/P10rJaP
System information
Additional context
Would my schema have something to do with it?
The text was updated successfully, but these errors were encountered: