Return 404 when update to table after signUp

[tawjaw]

I am following the stripe next example.
I have two tables users and settings. after insert to auth.users I create new record in both tables.
both tables have policy to allow select and update to user.

my query

create extension if not exists moddatetime schema extensions;

create table users (
  -- UUID from auth.users
  id uuid references auth.users not null primary key,
  first_name text,
  last_name text,
  is_teacher boolean default false,
  inserted_at timestamp with time zone DEFAULT timezone('utc'::text, now()) NOT NULL,
  updated_at timestamp with time zone DEFAULT timezone('utc'::text, now()) NOT NULL
);

create trigger handle_updated_at before update on users 
  for each row execute procedure moddatetime (updated_at);

alter table users enable row level security;
create policy "Can view own user data." on users for select using (auth.uid() = id);
create policy "Can update own user data." on users for update using (auth.uid() = id);

create table settings (
  -- UUID from auth.users
  id uuid references auth.users not null primary key,
  language text default 'English',
  theme text default 'Light',
  inserted_at timestamp with time zone DEFAULT timezone('utc'::text, now()) NOT NULL,
  updated_at timestamp with time zone DEFAULT timezone('utc'::text, now()) NOT NULL
);

-- this trigger will set the "updated_at" column to the current timestamp for every update
create trigger handle_updated_at before update on settings 
  for each row execute procedure moddatetime (updated_at);

alter table settings enable row level security;
create policy "Can view own user data." on settings for select using (auth.uid() = id);
create policy "Can update own user data." on settings for update using (auth.uid() = id);


create function public.handle_new_user() 
returns trigger as $$
begin
  insert into public.users (id, first_name, last_name)
  values (new.id, new.raw_user_meta_data->>'first_name', new.raw_user_meta_data->>'last_name');
  insert into public.settings (id)
  values(new.id);
  return new;
end;
$$ language plpgsql security definer;
create trigger on_auth_user_created
  after insert on auth.users
  for each row execute procedure public.handle_new_user();

CREATE FUNCTION public.delete_user() 
returns trigger as $$
begin
  delete from public.users 
  WHERE id = old.id;
  return old;
  delete from public.settings 
  WHERE id = old.id;
  return old;
end;
$$ language plpgsql security definer;
create trigger on_auth_user_deleted
  before delete on auth.users
  for each row execute procedure public.delete_user();

to sign up:

export async function signUp(userInfo: UserSignUpInfo) {
  const { error, user } = await supabase.auth.signUp({
    email: userInfo.email,
    password: userInfo.password
  });
  if (error) {
    console.log({ type: "error", content: error.message });
  } else {
    if (user) {
      await supabase
        .from("users")
        .update({
          first_name: userInfo.firstName,
          last_name: userInfo.lastName
        })
        .eq("id", user.id);
    } else {
      console.log({
        type: "note",
        content: "Check your email for the confirmation link."
      });
    }
  }
}

Sign up works, the rows are created in the tables. but the update returns 404

browser-ponyfill.js?5d61:517 PATCH https://gjrzdkxobmxnspyyhqmq.supabase.co/rest/v1/users?id=eq.51920a0b-07a3-4fb3-acfb-2d0d6f38392d 404

am I missing something?

[steve-chavez]

but the update returns 404

This will happen if the .update(..).eq("id", user.id) doesn't update any row. Perhaps your RLS policies are not allowing the UPDATE?

[tawjaw]

alter table users enable row level security;
create policy "Can view own user data." on users for select using (auth.uid() = id);
create policy "Can update own user data." on users for update using (auth.uid() = id);

It allows update