So ... I'm using Supabase on my own site that uses SSR. I'm managing to do the login using magic links, by getting the URL hash and storing as a cookie. Then I've created my own

getSupabase

method for the backend that retrieves the JWT from the cookie and sets the session using

supabase.auth.setSesssion(...)

That all works nicely and I can call the api etc. Problem is when I try to logout. I've tried a bunch of things. I delete the cookies and try to call

setSession

and

refreshSession

(which shouldn't work as it has no tokens to work on anymore from the cookies) but it still returns a user until I manually refresh the page again. What am I doing wrong?

Does anyone know how to enable sign up, sign in, storing and retrieving data from supabase in Vue 3?

How exactly does a client unsub from a realtime channel (Postgres CDC)? From the docs, there is

removeChannel()

which unsubs and 'removes' the channel from client. What does the remove part mean, if multiple clients are connected to the channel, and one client does a

removeChannel()

with that channels' name, does it also end the channel for the other clients? And there is also a

supabase.channel().unsubscribe()

which 'unsubscribes from server events and instructs server to terminate'...

JavaScript
// snippet from CommentItem component
// LISTEN FOR WHEN THE COMMENT IS UPDATED OR DELETED
    useEffect(() => {
        const { id: commentID } = commentData;
        const channelName = `public:comments:id=eq.${commentID}`;
        supabase
            .channel(channelName)
            .on(
                "postgres_changes",
                {
                    event: "UPDATE",
                    schema: "public",
                    table: "comments",
                    filter: `id=eq.${commentID}`,
                },
                onCommentUpdated
            )
            .on(
                "postgres_changes",
                {
                    event: "DELETE",
                    schema: "public",
                    table: "comments",
                    filter: `id=eq.${commentID}`,
                },
                onCommentDeleted
            )
            .subscribe();
        return () => supabase.removeChannel(channelName);
    }, [commentData, onCommentDeleted, onCommentUpdated]);

I just want that when the commentItem component unmounts, it should stop listening for those postgres changes on the comments table.

This is the error code from dev console

Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app

Hey how can i create a function using management api. To be more specific i need to add the definition of the function using management api... is it possible ?

Can anyone provide an example of how to use NextJS getStaticPaths and getStaticProps with the new

@supabase/auth-helpers-react

and

@supabase/auth-helpers-nextjs

packages. Every time I try and get it to work myself I end up with useContext errors as the useSupabaseClient() hook is being called outside of the main function.

Is there a way to configure supabase to run at port 3001 since it collides with remix running on port 3000. Can it be done after supabase init? I can't find the docker files

Hi guys! I'm trying to create a local development environment from an existing remote project. Following the guide at https://supabase.com/docs/guides/cli/local-development, npx supabase init npx supabase start npx supabase db remote commit npx supabase db reset I get the following error running the reset command:

Error: ERROR: relation "graphql.schema_version" does not exist (SQLSTATE 42P01)
At statement 125:                                                                                   
                                                                                  
                                                                                  
--                                                                                
-- Name: TABLE "schema_version"; Type: ACL; Schema: graphql; Owner: supabase_admin
--                                                                                
                                                                                  
GRANT ALL ON TABLE "graphql"."schema_version" TO "postgres";

Looking at the generated migration file, it doesn't seem to create the table graphql.schema_version. I'm guessing the CLI creates a different type of base database locally than what is hosted remotely? The remote project is 4-5 months old and been done entirely in production. Do you guys know what I can do? Is there a better way to migrate the db, a way to ensure local is the same version as remote, or a safe way to upgrade the remote db? My supabase CLI version is 1.12.2 Best regards Donny

Just tried using prisma to see if the supabase-js client is the issue -- same result

I'm loosing my mind trying to debug this -- I'm not convinced it's not an issue with my code but I've been at testing every piece for hours and hours now.... It seems like my boolean data is not updating --- UNLESS it is only one field at a time that I'm updating...... Whaaaat. Also, to make it worse: the result i get back from a supabase client query AFTER updating a row is correct -- but it doesn't actually save in the database. The code looks regular:

ts
  const {data} = await supabaseClient.from("subscriptions")
    .update({...subscriptionData}) // includes {"isSubscribed": true}
    .match({subscriberId: sub.userId})
    .select('subscriberId,isSubscribed')

  console.log(data) 
// {"subscriberId": 4926568, "isSubscribed": true}

BUT sql editor on dashboard returns

isSubscribed: false

I also tried using prisma, same problem. Doesn't save the updates....

If I have simple relationship where each playlist includes a list of tracks...

sql
CREATE TABLE public.playlists (
    id bigint generated by default as identity primary key,
    track_id bigint references public.tracks NOT NULL
);
CREATE TABLE public.tracks (
    id bigint generated by default as identity primary key,
    title text NOT NULL,
    artist_name text
);

And then access this with a query like this...

ts
const { data } = await supabase
  .from('playlists')
  .select(`
    id,
    tracks (
      title,
      artist_name
    )
  `)

I'd imagined that

tracks.title

could only be either a

string

or

null

type so I could use

tracks?.title

to make Typescript happy. But my typescript is giving errors if I use either

tracks.title

or

tracks?.title

ts
Property 'title' does not exist on type '({ title: string; } & { artist_name: string | null; }) | ({ title: string; } & { artist_name: string | null; })[]'.
Property 'title' does not exist on type '({ title: string; } & { artist_name: string | null; })[]'.

What am I missing? Also, semantically, shouldn't this relationship name be better changed to

track

from

tracks

as it is singular? Thanks!

Simple question... what's wrong with this postgres function?

SELECT * FROM textures ORDER BY id DESC LIMIT 1;

Trying to select the most recent row.

This is probably a silly question, but how do I invite other people to work on a project with me? I need to give access to the table editor to someone else

I'm looking for a tool chain that supports up() and down() migrations and plays well with the supabase echosystem from local > staging > production. For you guys running multiple environments, what are you using?

I am listening to

UPDATE

for changes in a DB row using realtime, however the response I get on the

new

property of the payload doesn't include all the data from that row. Specifically querying the db row does bring back the complete dataset as expected. Is this correct behavior?

I have many following auth errors in web console. "FATAL Failed to load configuration required key GOTRUE_DB_DRIVER missing value" How can I fix it?

I have a table that has a few thousand rows that I need to process. I want to process the data in chunks. How do I paginate the requests?

Not sure why this happen, been looking online but found no solution, I did not enable RLS and did turn on replication for the table. Any idea?

In my SvelteKit app, I need to pass the user's access token & refresh token to an API endpoint, set up an auth session for the user, then fire off some authenticated requests to Supabase. It's not working, though. Details: First, I fire off a request to an API endpoint like this, passing along the user's access token and refresh token:

ts
const userSession = (await supabase.auth.getSession()).data.session;
const response = await fetch('/api/stripe-checkout-session', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    accessToken: userSession?.access_token ?? '',
    refreshToken: userSession?.refresh_token ?? '',
  })
});

The request handler function for that API endpoint looks like this:

ts
export async function POST(event: RequestEvent): Promise<Response> {
    const { accessToken, refreshToken } = await event.request.json();

    const { data: setSessionData, error: setSessionError } = await supabase.auth.setSession({
        access_token: accessToken,
        refresh_token: refreshToken,
    });

        // 👇 Results in `{ session: null }`
    const { data: getSessionData, error: getSessionError } = await supabase.auth.getSession();
}

When I run

console.log(setSessionData)

, I get this:

ts
{
  session: {
    access_token: 'access-token-goes-here',
    refresh_token: 'refresh-token-goes-here',
    user: { ... },
    token_type: 'bearer',
    expires_in: 2402.638000011444,
    expires_at: 1668490476
  },
  user: {
    id: 'user-id-goes-here',
    aud: 'authenticated',
    role: 'authenticated',
    // ...
  }
}

Hi! I followed the documentation to create a login page using Supabase's Auth UI. My code looks like this:

ts
import { Auth, ThemeSupa } from '@supabase/auth-ui-react'
import { useSupabaseClient } from '@supabase/auth-helpers-react'

export default function Login() {
  const supabaseClient = useSupabaseClient()
  return (
    <Auth
      supabaseClient={supabaseClient}
      appeararance={{ theme: ThemeSupa }}
      theme="dark"
      socialLayout='horizontal'
      redirectTo="http://localhost:3000/"
    />
  )
}

But my UI ends up looking like the image attached. Also, the redirect does not work. I am still able to login and logout but its just the styling and redirect that is the issue. Thank you!

Any reasons why this code called from the front end wouldn't embed my redirectTo string, instead still uses localhost? This is the string it emails the user:

https://.....supabase.co/auth/v1/verify?token=cbf72dec7017df95f6e91762124ef76943a367eb441af09c9e8f4f1e&type=recovery&redirect_to=http://localhost:4200/

Is it possible to get the auth tokens from an account loggin via auth? In my case i need the users auth and secret token, with nextauth i can get them, i want to know if supabase provides them on response

Continued working on up my SvelteKit + Supabase Auth Helpers project from yesterday... tried signing in, and... suddenly I'm getting a

500

error when Supabase tries to apply auth actions.

Unexpected token 'I', "Invalid request body" is not valid JSON
SyntaxError: Unexpected token 'I', "Invalid request body" is not valid JSON

?! Only a few minor changes to the project from what I pushed to production yesterday (and which works). Cannot for the life of me see what suddenly changed. This error happens in

npm run dev

and

npm run build

. Here's the DevTools window: Any ideas? Where should I look?

As i cant refer text to text on relations, I need to do a query to fetch like following: Sum all Total Revenue where store_royalties.Label = music_label_name => ref Owner.uuid = Auth.uuid Or maybe I Should premodel the data to add a INT at Store Royalties and refer where Label Name = Label_ID to link them for faster sums later? I'm so stuck on this and Would LOVE to have a hand on how to solve it...

Hi. I have this function that when i use the rpc function of supabase returns me the following.

CREATE OR REPLACE FUNCTION close_advertisements (lat float, lng float)
    RETURNS SETOF public.advertisements
    LANGUAGE plpgsql
    AS $$
BEGIN
    RETURN query (
        SELECT
            *
        FROM
            advertisements
        WHERE
            ST_DWithin (geom, ST_SetSRID (ST_MakePoint (lng, lat), 4326), 10000));
END;
$$
SECURITY DEFINER SET search_path = extensions, public, pg_temp;

Error message: "Could not find the public.close_advertisements() function or the public.close_advertisements function with a single unnamed json or jsonb parameter in the schema cache" I added the security definer to try an make it visible but without success

I want to capture,parse & store json from an external webhook. It looks like edge functions can serve that purpose... are there any examples or boiler plate example functions, that capture json elements and store to the DB? (saw the stripe tutorial, but it did not included storing data to db)

I'm trying to write some simple test scripts that sign in a test user and access the database, but I keep getting an auth error. It's like the client library isn't storing the auth token or something. The error happens in my Jest test script, but also just from a simple node script like:

import { createClient } from '@supabase/supabase-js'

const PUBLIC_SUPABASE_URL="https://xxxxxxxxx.supabase.co";
const PUBLIC_SUPABASE_ANON_KEY="xxxxxxxxxxxxx";

const supabase = createClient(PUBLIC_SUPABASE_URL, PUBLIC_SUPABASE_ANON_KEY);

const result = await supabase.auth.signInWithPassword({
  email: 'bob@example.com',
  password: 'mypassword',
});
console.log('result', result);
console.log('user', await supabase.auth.getUser());

The signInWithPassword() call returns the correct session and user, but the getUser() call returns the error:

AuthApiError: invalid claim: missing sub claim

And any other call seems to be unauthenticated.

Hey y'all! I want to expose a schema so that I can interact with it using supabase-js in my local development setup for edge functions but I'm running into issues. I'm using

createClient(URL, KEY, {db: {schema: 'stats'}} )

as seen in the reference guide for supabase-js [1]. The error I get when I run this locally is:

error: TS2322 [ERROR]: Type '"stats"' is not assignable to type '"public"'

. I have verified that this schema does exist in the local database when I run psql directly. According to the docs, you have to expose new schemas to the API via the supabase dashboard by going to

Settings > API Settings > Exposed Schemas

and adding it manually there. Unfortunately, while this works for the production dashboard I can't get to that setting on my local dashboard. What can I do to expose a schema I made on local? [1]: https://supabase.com/docs/reference/javascript/initializing#api-schemas

I trying to insert a data uri string to a text datatype column . i get this error when i do so

Whenever I am entering a new row in my database it is showing in UTC but I want in Indian standard time IST +5:30 So I tried to use timestamptz but stuck at its default value (now() AT TIME ZONE 'utc'::text) I tried to replace the UTC with IST but no use I am still getting UTC time in my row