Issues with User Authentication & Missing ID Field in Supabase (Bolt.new Integration)

[elm1313]

Hello everyone,
I am pretty new at all this, but here is my issue that I am seeking guidance on. I have reached out to Supabase support and submitted a ticket, but being a weekend, I am not sure I will hear back till next week, and hoping I might get some direction before then. :)
I’m integrating Bolt.new with Supabase for a project, and I’m encountering an issue during the user authentication process. Specifically, when trying to create a new user, I get the following error:

ERROR: 23502: null value in column "id" of relation "users" violates not-null constraint.

Here’s the situation:
I am using @supabase/supabase-js for authentication, and Bolt.new for the front-end and back-end of my app.
The error happens because the id field in the users table is not being generated or populated correctly when a user is created.
The issue seems to be related to how Supabase is handling user creation, particularly with the missing id column, even though other fields like email and encrypted_password are being populated.
Has anyone else faced this issue or encountered similar problems when working with Supabase and Bolt.new together?
If so, how did you resolve it, or is there any guidance on how to configure the id field properly for user authentication in Supabase?

Any help would be appreciated!

Thanks in advance!
ELM

[GaryAustin1]

Do you know the error is about the auth.users table? Could it be you have a public users table that is setup with an insert trigger on auth.users and that is what is failing?

You should check if you have a public table users and look in the Postgres logs.