Cannot create new branch due to modified auth.jwt() — need help resetting to default
Hi everyone,
I’m running into an issue with my Supabase project:
In the past, when the auth schema was still editable, I updated the auth.jwt() function for development purposes.
Now, Supabase has locked down the auth schema (owned by supabase_auth_admin).
Because of my past migration, whenever I try to create a new branch in Supabase Studio, the process fails. It errors out on auth.jwt() with:
permission denied for schema auth
This means I can’t spin up a new branch to continue feature development.
What I need help with:
How can I reset the auth.jwt() function back to the default implementation that Supabase ships with?
Or is there a way to skip/repair that old migration so branch creation works again?
If anyone has faced this before or knows how the Supabase team can restore the default auth schema functions, please let me know
Thanks in advance!
I’m running into an issue with my Supabase project:
In the past, when the auth schema was still editable, I updated the auth.jwt() function for development purposes.
Now, Supabase has locked down the auth schema (owned by supabase_auth_admin).
Because of my past migration, whenever I try to create a new branch in Supabase Studio, the process fails. It errors out on auth.jwt() with:
permission denied for schema auth
This means I can’t spin up a new branch to continue feature development.
What I need help with:
How can I reset the auth.jwt() function back to the default implementation that Supabase ships with?
Or is there a way to skip/repair that old migration so branch creation works again?
If anyone has faced this before or knows how the Supabase team can restore the default auth schema functions, please let me know
Thanks in advance!
