Signout Button currently uses an API call instead of native supabase, and that means that when an error is thrown on signout, all that happens is a user is thrown into an endless loading on signout. This can be fixed by using a server action on the click of the signout button, or by using a supabase client that runs on the client-side.
Signout Button currently uses an API call instead of native supabase, and that means that when an error is thrown on signout, all that happens is a user is thrown into an endless loading on signout. This can be fixed by using a server action on the click of the signout button, or by using a supabase client that runs on the client-side.
The admin portal can be used for reference.