Was checking the documentation and didn't find how to do signup with custom fields. Can we just pass additional fields in

auth.signUp

? I'm reading this: https://supabase.io/docs/reference/javascript/auth-signup

What do you mean by custom fields? If I'm understanding properly, you are probably looking to create a separate users or profiles table.

I was thinking about saving first name, last name for the user while signup

The

auth.users

table is not exposed to the public api. Take alook at this guide: https://supabase.io/docs/guides/auth/managing-user-data

You could make a trigger so the profile gets created automatically, or, what I do in most cases... is just upsert a new row on the public users table with the auth.user.id as the key.

I see. Thanks @romlytech!

No problem. Everybody has their own way of doing things so perhaps you will find what suits your needs best. In my case, I typically allow the signup which gets the user into the application but do not allow any actions within the application until they've completed their profile.

hi! how would I move existing users to profiles?

You aren't necessarily "moving" them. The users still exist on

auth.users

- you are just making another

public.profiles

(or whatever you decide to call it) where the primary key is the user's ID from the

auth.users

table.

In two of my applications, I just use

upsert

for the

public.profiles

table on my Edit Profile pages and don't worry if they exist or not. The users signup, login then are redirected to the edit profile page.

I have a related question. I have an update profile page where I do an upsert, but because my profile id is generated automatically by supabase- my upsert won’t work. The upsert requires sending primary key on payload , but if it’s the first time a profile os created, I won’t have a primary key Do I need to generate my keys on the client?

thanks, trying to wrap my head around it

Posted this in JS channel, maybe someone could help with this one. I'm having an issue with token refresh in NextJS. Once the token expires, I can't access protected routes because user is null. Has anyone else encountered this as well?

Can anyone help me, how do I download a copy of my database?

sure

myself i am using a sql client for that

there are many available online

I often use dbeaver since it is opensource 🙂

Once you have added the database; just right-click on your schema to export the data

Why there are two different guides for self-hosting? (https://supabase.io/docs/guides/self-hosting) and (https://supabase.io/docs/guides/local-development)

google oauth is bugged on React Native

javascript
import { createClient } from '@supabase/supabase-js';

const supabaseUrl = process.env.SUPABASE_URL;
const supabaseAnonKey = process.env.SUPABASE_ANON_KEY;

export const supabase = createClient(supabaseUrl, supabaseAnonKey);

env
SUPABASE_URL=<url-here>
SUPABASE_ANON_KEY=<key-here>

So I setup the client, but in my NextJS app I keep getting an error

Unhandled Runtime Error
Error: supabaseUrl is required.

What's going on here? When I console.log the url/key they are both being read in properly from the .env file.

I'm using https://github.com/vercel/nextjs-subscription-payments I was having no problems with my app. Then I added an

email

field to

public.users

(which is a table that ships with the starter project). Now, user sign up is failing. I'm getting

{message: "Database error saving new user", status: 500}

. This is documented in several GitHub issues for Supabase but the solutions there aren't helping me. I've tried renaming

public.users

to

public.accounts

. Also tried deleting the

handle_new_user

function that ships with that starter project, since I figured that might be responsible, but I can't. I get an error saying

Deleting handle_new_user failed: cannot drop function handle_new_user() because other objects depend on it

. Also tried updating

handle_new_user

to the following, where I've added the logic for the new

email

field, in case that's the issue:

begin
  insert into public.accounts (id, full_name, avatar_url, email)
  values (new.id, new.raw_user_meta_data->>'full_name', new.raw_user_meta_data->>'avatar_url', new.raw_user_meta_data->>'email');
  return new;
end;

The

email

field on

accounts

is nullable by the way. Any ideas gratefully appreciated since my SaaS business is totally broken right now, with no one being able to sign up and pay!

I should add that inviting new users via the Supabase dashboard is also broken, with the same error:

Inviting user failed: Database error saving new user

Phew, fixed this. I ran

DROP FUNCTION IF EXISTS handle_new_user cascade;

which was suggested in this GitHub issue: https://github.com/supabase/supabase/issues/563

I'm using DBMate for migrations, which creates a schema_migrations in the public schema. How should I make sure that it isn't queryable? I tried turning on RLS but it seems like since the Postgrest server is using the postgres user, people would still be able to access it?

I think the purpose is a little different! With self-hosting you'd be deploying the backend yourself, so you should for example configure all the production DB secrets, whereas with local dev you can just use the defaults

Why is the database URL for the postgrest service not "postgres://authenticator:postgres@db:5432/postgres"?

Because it's not hosted inside Postgres database - it's a REST API that runs outside the database