Hey, have a great day 🌥️ I have a question, how can do or how can handle the

supabase.auth.user()

on the server side, the main reason is cuz I'm trying to create a route middleware with nuxt.js

I'm currently using

@supabase/auth-helpers-nextjs

you should give it a try

yo is anyone having this weird behavior with real time subscription, the status of it shows, CLOSED then SUBSCRIBED then CLOSED again, I try to insert a row in a table, and it doesn't update it in real time, but when I go to another tab and return to my app it shows the newly added row?

I try to turn off react strict mode, but still the same

So i am currently trying to create a SignUp with Discord and i run into the following problem. On Callback i get this Error. I double checked all URL's and Key's and only used the official function example:

ts
async function signInWithDiscord() {
  const { user, session, error } = await supabase.auth.signIn({
    provider: 'discord',
  })
}

The user anyhow, gets added to the Database successfully, so i am kinda confused whats going on now 0.o

Hi, I'd like to use the new Next Js Auth components, but struggling with how to style up the buttons & text. I can style up individual components from Supabase UI - e.g. set the backgroundColor of a button by passing style : {backgroundColor : 'Red"} but once inside the Auth component I can't figure out how to style up the subcomponents. Is there any guide to how to use the style props of the Auth components to fully style them up? Thanks

Discord SignIn Problem

I'm trying to verify a user JWT. My current setup is a React frontend that sends the JWT over a websocket to a remote backend running Node.js. This backend communicates with Supabase along with the React frontend. The front-end works perfectly fine (I can sign up through any service, I can fetch stuff from the DB protected by auth-based RLS rules, etc). However, when I attempt to verify (both in Remix's frontend/backend and on the Node.js backend), I'm immediately met with a 401 error (

"Invalid token: token is expired by 8m21s"

). I tested this further and attempted to refresh the token only to be met with the same error but with a time of

1s

. Can anyone help in regards to why my JWTs are immediately expiring after being generated?

Anyone facing the issue where the real time works sometimes and breaks sometimes? The client is subscribing but it is not listening to any table updates

ping

I don't want to use RLS policies and would like to manage the authorization stuff on my node-server. For some reason, I didn't find anything helpful on the web regarding best practices so my approach is to create a supabase client on the server with the service role key so that it can bypass the RLS. Is that an adequate approach?

Node auth

Anyone good with edge functions and how to import correctly?

javascript
// index.ts
import { serve } from "https://deno.land/std@0.131.0/http/server.ts"
import puppeteer from "https://deno.land/x/puppeteer@9.0.0/mod.ts";
import { cheerio } from "https://deno.land/x/cheerio@1.0.6/mod.ts";

serve(async (req) => {
  const { url } = await req.json()
  const browser = await puppeteer.launch();
  const page = await browser.newPage();
  await page.goto(url);
  const html = await page.content();
  const $ = cheerio.load(html);
  const title = $('title');
  const data = {
    title: title,
  }

  return new Response(
    JSON.stringify(data),
    { headers: { "Content-Type": "application/json" } },
  )
})

on supabase functions deploy myfunc returns:

bash
Error: Error bundling function: exit status 1
error: TS2339 [ERROR]: Property 'load' does not exist on type '(selector: any, context: any, root: any, opts: any) => any'.
  const $ = cheerio.load(html);

Many thanks in advance, Joe

Hi did anyone tried using const { error } = await supabase.auth.signOut() to sign a user out but the access token is still there even after signing out?

The jwt is still valid until it expires. The refresh token though gets invalidated on the server.

thanks!

Trying to get the realtime to work, got replication setup and I'm getting updates but all the updates I get come back with unauthorized.

We've got our own JWT authentication so I'm really confused how we're meant to authenticate for realtime

You probably need to add a role to the jwt either 'anon' or 'authenticated'

Could I get a little more detail on how to do this?

Like how do I then authenticate the supabaseClient?

(also no clue how to "add a role to the jwt")

In the DB, under Roles its showing I have no anon's connected as well which is strange

And the api logs does show my websocket connections

Creating a nuxt3 app and I'm wanting to use a private bucket on Supabase for hosting images, how can I get the URL for

<img src="xxx">

? I can only seem to get it to work by making it public.

https://supabase.com/docs/reference/javascript/storage-from-createsignedurl createSignedUrl is the way to get a storage file url with token for private buckets. You do need to allow select access RLS policy to get the signed url.

Thanks @garyaustin , looks like that works. Is there a way to make it not expire? Or alternatively is there any limit? If not I can make it large

Not sure what the upper limit, but you can make as many seconds as desired. The token is just a jwt with an expiration “time”. At some point though you might as well have a public bucket (only difference is url does not expire) with a hard to guess name.

Fair point, the web app is just for my family and will have images of us hence why I wanted it for authenticated users only. However I also wanted to avoid performing an api call per image to get the url every time someone opened the web app. I thought I might be able to createSignedUrl when the image is uploaded and store the URL in a table. Therefore being able to pull the url of all images at once 🙂