It's a good idea, maybe add a request in the PostgREST github page.

Hey, this indeed does work. This is the method I was trying before actually, however I did not notice the 'confirm' email!

Thanks for confirming this! I appreciate it!

No worries, I'm not sure why it isn't in the main docs so I have opened a PR.

@User - some more info on this link, as I am now working to "do something" with the confirmation email in my app - https://supabase.io/docs/gotrue/client/api-updateuser

Just out of curiosity: how many of you are using Supabase in an SPA?

Any suggestions on this? 🙂

Am I better off using

supabase.auth.api.setAuthCookie

and

supabase.auth.api.getUserByCookie

?

This is kind of where I’m at too. I’m needing to store the access token in a cookie to use in further requests after the user is logged in. Take a look at this article, it’s what I’ve been going off of lately: https://dev.to/dabit3/magic-link-authentication-and-route-controls-with-supabase-and-next-js-leo

Basically you create a ‘/api/auth’ route (not sure if you’re using NextJS), which sets the cookie server-side, then on the client side you can use ‘getUserByCookie’

Thanks I'll give it a go 🙂

Let me know if you have any questions!

I think I'm doing it wrong....

const { user } = await supabase.auth.api.getUserByCookie(req.headers.token);
const { data, error } = await getSettings(user.id);

user.id is always null?

js
if(users){
  console.log(user)
}

have you tried something like this? just in case

Ah I think my fetcher is broken... getting 500 error

that'll dew et

500 error is internal server error. Could you contact support by using the Feedback widget in your Supabase dashboard? @User

Supabase* 😉

Fixed. haha

It's probably my code first though... I'm confusing so many things here

yea, i got some 500 errors and it wans't supabase

Ok... The call from /pages/account

const { user, session } = useUser();
  const { data, error } = useSWR(
    user ? ['/api/settings', session.access_token] : null,
    fetcher
  );

fetcher

export const fetcher = (url, token) => {
  return fetch(url, {
    method: 'GET',
    headers: new Headers({ 'Content-Type': 'application/json', token }),
    credentials: 'same-origin'
  }).then((res) => {
    return res.json();
  });
};

/pages/api/auth

import type { NextApiRequest, NextApiResponse } from 'next';
import supabase from '@utils/supabase';

const handler = async (
  req: NextApiRequest,
  res: NextApiResponse
): Promise<void> => {
  supabase.auth.api.setAuthCookie(req, res);
};

export default handler;

So the SWR call itself is failing and never running the settings api

Session token definitely exists

One thing is for sure, the fact i've gotten this far is a testament to supabase 🤣

Might need to return a response from the auth handler? Try adding

res.status(200).end()

at the end of your handler

@User ^

Hmm that didn't fix it but you are probably right - I stole that code from https://github.com/dabit3/supabase-nextjs-auth

const { user } = await supabase.auth.api.getUserByCookie(req.headers.token);

returns null