First GitHub sourced migration failing due to auth schema

Hello, I am trying out Supabase branching on an existing project. I have a single migration file synced in remote and local describing the existing state of my database, as well as a further small migration file describing a public table drop. For some reason the migration is failing when pushing to GitHub and Supabase tries to build it on a preview branch. The error is

ERROR: permission denied for schema auth (SQLSTATE 42501)
At statement: 0
create type "auth"."oauth_authorization_status" as enum ('pending', 'approved', 'denied', 'expired')

ERROR: permission denied for schema auth (SQLSTATE 42501)
At statement: 0
create type "auth"."oauth_authorization_status" as enum ('pending', 'approved', 'denied', 'expired')

If I run

supabase db reset

supabase db reset

the migration applies correctly and is reflected in the web view. It only fails when trying to build the preview branch. Supabase CLI is up to date and importantly my migration files do not contain this statement. Please let me know if this is a known issue or if any feedback can be provided. Thank you.

Supabase•5mo ago•

4 replies

Owain

First GitHub sourced migration failing due to auth schema

ERROR: permission denied for schema auth (SQLSTATE 42501)
At statement: 0
create type "auth"."oauth_authorization_status" as enum ('pending', 'approved', 'denied', 'expired')

ERROR: permission denied for schema auth (SQLSTATE 42501)
At statement: 0
create type "auth"."oauth_authorization_status" as enum ('pending', 'approved', 'denied', 'expired')

If I run

supabase db reset

supabase db reset

First GitHub sourced migration failing due to auth schema

Similar Threads

First GitHub sourced migration failing due to auth schema

Similar Threads

Similar Threads

Similar Threads