500 error supabase sign up

ダッシュボードからユーザーを新規登録しようとすると、エラーになる

Failed to invite user: failed to make invite request: Database error saving new user

{
    "code": 500,
    "error_code": "unexpected_failure",
    "msg": "Database error creating new user",
    "error_id": "890eb532f7ed2624-NRT"
}

katayama8000

Check your dashboard postgres logs. 500 on signup is almost always you have an auth.users trigger function failing.

katayama8000

Probably something wrong with your auth.uses trigger if you have one. Look in the Postgres logs in the dashboard for the error.

katayama8000

dashbord を見ろと

katayama8000

{
  "file": null,
  "host": "db-nvldqfptrmwokpagptwh",
  "metadata": [],
  "parsed": [
    {
      "application_name": null,
      "backend_type": "client backend",
      "command_tag": "INSERT",
      "connection_from": "127.0.0.1:58874",
      "context": "PL/pgSQL function public.handle_new_user() line 3 at SQL statement",
      "database_name": "postgres",
      "detail": null,
      "error_severity": "ERROR",
      "hint": null,
      "internal_query": "insert into public.profiles (id, full_name, avatar_url)\n  values (new.id, new.raw_user_meta_data->>'full_name', new.raw_user_meta_data->>'avatar_url')",
      "internal_query_pos": 13,
      "leader_pid": null,
      "location": null,
      "process_id": 318285,
      "query": "INSERT INTO \"users\" (\"aud\", \"banned_until\", \"confirmation_sent_at\", \"confirmation_token\", \"created_at\", \"deleted_at\", \"email\", \"email_change\", \"email_change_confirm_status\", \"email_change_sent_at\", \"email_change_token_current\", \"email_change_token_new\", \"email_confirmed_at\", \"encrypted_password\", \"id\", \"instance_id\", \"invited_at\", \"is_anonymous\", \"is_sso_user\", \"last_sign_in_at\", \"phone\", \"phone_change\", \"phone_change_sent_at\", \"phone_change_token\", \"phone_confirmed_at\", \"raw_app_meta_data\", \"raw_user_meta_data\", \"reauthentication_sent_at\", \"reauthentication_token\", \"recovery_sent_at\", \"recovery_token\", \"role\", \"updated_at\") VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16, $17, $18, $19, $20, $21, $22, $23, $24, $25, $26, $27, $28, $29, $30, $31, $32, $33)",
      "query_id": 3813874241608362000,
      "query_pos": null,
      "session_id": "66653d02.4db4d",
      "session_line_num": 7,
      "session_start_time": "2024-06-09 05:26:26 UTC",
      "sql_state_code": "42P01",
      "timestamp": "2024-06-09 05:27:08.302 UTC",
      "transaction_id": 1960,
      "user_name": "supabase_auth_admin",
      "virtual_transaction_id": "8/18033"
    }
  ],
  "parsed_from": null,
  "project": null,
  "source_type": null
}

katayama8000

 "insert into public.profiles (id, full_name, avatar_url)\n  values (new.id, new.raw_user_meta_data->>'full_name', new.raw_user_meta_data->>'avatar_url')",

katayama8000

profiles table がない

katayama8000

functions を削除したいが、trigger に紐づいている

katayama8000

The following schemas are managed by Supabase and are currently protected from write access through the dashboard.

auth
cron
extensions
information_schema
net
pgsodium
pgsodium_masks
pgbouncer
pgtle
realtime
storage
supabase_functions
supabase_migrations
vault
graphql
graphql_public
These schemas are critical to the functionality of your Supabase project and hence we highly recommend not altering them.

You can, however, still interact with those schemas through the SQL Editor although we advise you only do so if you know what you are doing.

katayama8000

trigger の削除は SQLeditor を使えとのこと