SOLVED Empty Array

[hoesmean]

SOLVED

Hello i get empty array when i query my data?

is anyone know how to fix i

t

?

[realPrimoh]

Well, how did you solve this?

[joaodk3]

Hey!

I advise you to disable the RLS just to test if that is the problem. After this, you can enable it and create a specific Policy for your needs, that would be more secure and appropriate.

You can understand more about Postgres rls and policies here: https://www.postgresql.org/docs/current/ddl-rowsecurity.html

[shatmanyu]

Disabling RLS worked!!

[pcnoic]

I am not sure that disabling RLS is the go-to option for many of the folk here. Make sure you disable it knowing what potential security implication this might have for your app.

The OP disabling the RLS will lead to the listings table being exposed.

Adding a proper RLS policy instead of disabling it might be the safest path here.

[Santipac]

It depends on your policy settings, but in my case I forgot to add the “authenticated” role.

create policy "Allow authorized get access" 
on public.table for select 
to authenticated, anon
using ( true );

[mahabubx7]

Disabling the RLS solved my problem.

Thanks a lot 🫶
I was debugging and almost lost my mind 😆
You saved the day 🤝

[jordiyapz]

For future reader who are beginner in Supabase like I was, if your table has Row Level Security (RLS) enabled, add atleast a policy to allow reading for everyone. There is a template for that.

Check out the guide

[mattskinosix]

I love you, thank you

[jordiyapz]

Glad to hear that! 😁

[Sanan4li]

This thing wasted my 4 hours trying to figure out the issue in my code.

[edof]

man, you saved my life. trying to figure what's wrong with my code and you just give me solution

[TheSlavant]

what can i say, your advice keeps saving lives

[sanba-anass]

disabling rls does not work for me is there any thing that cause this?

[pandas9]

were you guys able to solve this since its the exact same for me I'm using NextJS14 with javascript and supabase-js as the lib. following the docs to the letter. I have tried everything. the funniest part is that i am able to add rows but the api returns an empty array when i try to read it.

yeah lol had same issue just hard refresh

[richardfwashington]

I didn't solve it per se. It just started working. I'm guessing some kind of caching the needed time to flush. But to be honest I'm unsure. If anyone has any light to shed on this I'm sure it would be appreciated.

[salim-mohamed-98]

i solved it by calling unstable_noStore() inside my page component. Converting my page component from static to dynamic(no caching). i think.

[avnogy]

nextjs 13, solved it by deleting .next/cache, rls was enabled at the start and next cached the empty response

[devmev10]

nextjs 13, solved it by deleting .next/cache, rls was enabled at the start and next cached the empty response

This worked!

[pandas9]

for anyone ending up here, for nextjs this is the solution

export const supabase = createClientComponentClient({
  options: {
    global: {
      fetch: createFetch({
        cache: "no-store",
      }),
    },
  },
});

'use server'
export const createFetch =
  (options: Pick<RequestInit, "next" | "cache">) =>
  (url: RequestInfo | URL, init?: RequestInit) => {
    return fetch(url, {
      ...init,
      ...options,
    });
  };

[hmtcelik]

works like a charm !

[sangrepura]

OK, I landed here because I had the same issue: RLS off, no errors, empty array using createClient from @supabase/supabase-js

createClientComponentClient() from @supabase/auth-helpers-nextjs did work, but then I quickly discovered that this package is being deprecated in favor of @supabase/ssrs

see this Reddit response

and this migration guide

Here is a minimal setup I used to get this working with their new server components package, @supabase/ssrs:

Step1:

uninstall @supabase/auth-helpers-nextjs

install @supabase/ssrs

Step 2:

env.locaL:

NEXT_PUBLIC_SUPABASE_URL=<my-url>
NEXT_PUBLIC_SUPABASE_ANON_KEY=<my-anon-key>

Step 3:

src/utils/supabase.ts:

import { createServerClient, type CookieOptions } from '@supabase/ssr'

export const supabase = (cookies: CookieOptions) => {
    const cookieStore = cookies()

    return createServerClient(
        process.env.NEXT_PUBLIC_SUPABASE_URL!,
        process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!,
        {
            cookies: {
                get(name: string) {
                    return cookieStore.get(name)?.value
                },
            },
        }
    )
}

Step 4:

src/app/myroute/page.tsx:

import { supabase } from "@/utils/supabase";
import { cookies } from "next/headers";

export default async function Page() {
  const { data } = await supabase(cookies).from("mytable").select();
  return <pre>{JSON.stringify(data, null, 2)}</pre>;
}

}

Step 5:

Navigate to http://localhost:3000/myroute and see your results

Step 6:

Don't forget to turn RLS back on!

[loud1990]

THANK YOU!!!

[Seokhyeon315]

I have a same issue. I am using Astro framework with latest version 4.0 and trying to get images from Supabase storage but it returns the empty array [] and error is null. When I look at the supabase dashboard, it seems there was request and response on the server, but I don't know why it returns empty array...

[jaxkashif34]

same problem with me. do you find any solution?

[vice7770]

Same issue, seems that sometimes it fails and other times comes as []. I think supabase auth(doesn't matter if on the server or not) has some problems. For what i notice in my testing, seems to be affected by high latency.

[vice7770]

Hello, Can you please provide me a time schedule today to talk. Im available all day. Thank you

…

On Wed, Sep 11, 2024, 23:42 Santiago Pacini ***@***.***> wrote: It depends on your policy configuration, but in my case I failed to add the “authenticated” role — Reply to this email directly, view it on GitHub <#3780 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APXXP44NH2SCX6SICXBXPA3ZWDBMNAVCNFSM5HKXRHQ2U5DIOJSWCZC7NNSXTOSENFZWG5LTONUW63SDN5WW2ZLOOQ5TCMBWGE4TQMZQ> . You are receiving this because you commented.Message ID: ***@***.***>