what is the best way to troubleshoot when RLS policies aren't working?

like, I have a basic rule that's like (uid() = agent_id), and it's not showing any items...

Hello, Is possible to change the response object from select? I want to rename "**categories**" into "**category**". Here is the code:

js
const { data, error } = await supabase
      .from<Balance>('balances')
      .select(
        `
      id, title, type, 
      categories(title)
        `
      )
      .order('created_at');

The current response:

json
[{"id":3,"title":"Lorem ipsum dolor sit amet","type":"income","categories":{"title":"Test"}},

The response that expected:

json
[{"id":3,"title":"Lorem ipsum dolor sit amet","type":"income","category":{"title":"Test"}},

Thanks.

@Deleted User can u try with

categories(title) as category

?

no luck, it's still the same

@Deleted User

category:categories(title)

?

oh, it works! Thank you

🚀

is there any way to get the user id of a new user when using passwordless login (magic link and phone OTP) to be able to store some data about the user and link it to their user account?

Is there a way to only auth users that I have invited previously?

How should I protect static paths? UseEffect? I am using nextjs and supabase/helpers

Cause withAuthRequired only works on SSR right?

useEffect & checking the user

hi please I have a problem I have not faced before:

I get this error: {message: 'JWSError JWSInvalidSignature'}

when I try to insert into my supabase table from my NUXT frontend

JWT error

Hi all. I have created a (supabase) function, but when I call it I get CORS error "No 'Access-Control-Allow-Origin' header is present on the requested resource.". Where can I add allowed origins? Thanks for the help!

you running supabase on client?

or you trying to use it on a nodejs server?

I’ve created a signup/login for a React + Firebase, setup. Can I use the same form, except, just switch out the firebase for Supabase?

CORS error No 'Access-Control-Allow-Origin'

Firebase to Supabase

Hi, have any of you tried to save the image with a multer. With response I have that the file was successfully saved, but in the supabase story I can only see the name of the photo and I cannot see the image.

js
const storage = multer.diskStorage({
  filename: (req, file, cb) => {
    cb(null, file.fieldname + '-' + Date.now());
  },
});
const upload = multer({ storage: storage });

server.post('/file', upload.any('file'), async (req, res) => {
  const imgFile = req.files[0].path;
  const imgName = req.files[0].filename;
  const { data, error } = await supabase.storage
    .from('avatars')
    .upload(`public/${imgName}`, imgFile, {
      cacheControl: '3600',
      upsert: false,
    });
  console.log(data);
  console.log(error);
  res.send(imgFile);
});
==================
reply from the server
{ Key: 'avatars/public/file-1648914887914' }
null
POST /file 200 534.654 ms - 52

I don't know much about that, but I do recommend converting images to base64

I made a second attempt and the result is similar, the photo is uploaded, but no preview.

js
const { decode } = require('base64-arraybuffer');
const storage = multer.diskStorage({
  filename: (req, file, cb) => {
    cb(null, file.fieldname + '-' + Date.now());
  },
});
const upload = multer({ storage: storage });

server.post('/file', upload.single('file'), async (req, res) => {
  const { file } = req;

  try {
    const { data, error } = await supabase.storage
      .from('avatars')
      .upload(`public/${file.originalname}`, decode(file), {
        contentType: `${file.mimetype}`,
      });
    console.log(data);
    console.log(error);
    res.send(data);
  } catch (err) {
    console.log(err);
  }
});

Maybe some of you know why I can't upload a photo.

I am sorry to say that I solved the problem, but spent a good couple of hours on it. I've tried various solutions, but these turn out to be the best.

js
const storage = multer.diskStorage({
  filename: (req, file, cb) => {
    cb(null, file.fieldname + '-' + Date.now() + path.extname(file.originalname));
  },
});

const upload = multer({ storage: storage });

server.post('/file', upload.single('file'), async (req, res) => {
  const { file } = req;
  const imageBuffer = await sharp(file.path).toBuffer();
  let id = uuidv4.v4();
  try {
    const { data, error } = await supabase.storage
      .from('avatars')
      .upload(`public/${id}`, imageBuffer, {
        contentType: `${file.mimetype}`,
        cacheControl: '3600',
        upsert: false,
        insert: true,
      });
    const { publicURL } = supabase.storage.from('avatars').getPublicUrl(`public/${id}`);
    console.log(data);
    console.log(error);
    res.json({ data, url: publicURL, err: error });
  } catch (err) {
    console.log(err);
  }
});

I'm currently testing coverage of migrating our serverless API from GatsbyCloud to SB Edge Fn. Our API utilises AWS for Dynamo and SES, Stripe and of course Supabase. The last two were not too bad thanks to the SB examples but aws-sdk was a real pain to get working in Deno, especially SES where the 'official' module on DenoLand is just plain broken due to incorrectly resolved dependancies served by jspm.dev. On Deno vanilla this is likely straightforward to resolve by building local dependancies but with SB functions there don't seem to be any controls to pass to Deno. FWIW I got both SES and Dynamo to work by switching to esm.sh with a specifically constructed URL, eg for SES: https://cdn.esm.sh/v74/@aws-sdk/client-ses@3.58.0/deno/client-ses.js

first of all you have to wrap await in async function, then use try catch to catch errors

You probably want to post an enhancement/bug issue on github. A dev is more likely to see it there and functions are still alpha so they are looking for feedback. https://github.com/supabase/supabase/issues