supabase: Database error finding user (when creating one), supabase-auth accessing public.users not auth.users
Bug report
Describe the bug
I setup local dev a while ago, and now implementing auth. However when I call supabaseClient.auth.signUp(...) and look at the results in the net panel of dev tools, I see a result code error 500 and contents {code: 500, msg: "Database error finding user", ...} when posting to http://localhost:8000/auth/v1/signup
System information
- OS: MacOS (latest)
- Browser: Chrome (latest)
- Version of supabase-js: 1.11.9
- Version of Node.js: v14.16.1
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 10
- Comments: 22 (9 by maintainers)
Commits related to this issue
- app models: add accounts model to database Cannot name the table `users` because of https://github.com/supabase/supabase/issues/1479 — committed to cmnord/jep by cmnord a year ago
- app models: add accounts model to database Cannot name the table `users` because of https://github.com/supabase/supabase/issues/1479 — committed to cmnord/jep by cmnord a year ago
- app models: add accounts model to database Cannot name the table `users` because of https://github.com/supabase/supabase/issues/1479 — committed to cmnord/jep by cmnord a year ago
- app models: add accounts model to database Cannot name the table `users` because of https://github.com/supabase/supabase/issues/1479 — committed to cmnord/jep by cmnord a year ago
- app models: add accounts model to database Cannot name the table `users` because of https://github.com/supabase/supabase/issues/1479 — committed to cmnord/jep by cmnord a year ago
- app models: add accounts model to database Cannot name the table `users` because of https://github.com/supabase/supabase/issues/1479 — committed to cmnord/jep by cmnord a year ago
Can we reopen this issue - still seeing this locally, and there isn’t a linked commit fixing this, it looks like the accepted solution is a workaround.
No. I had to rename the public.users to public.accounts.
@MaxAltena I’m not sure that it’s the same since you’re using the Supabase hosted version. Your problem sounds more similar to the one specified here.