Supabase Fetch Data Error : Cannot read properties of null (reading 'from')

message: “Cannot read properties of null (reading ‘from’)”

An error occurred while fetching data table in the supbase.

When I restart the supbase project, the data is loaded and the same error occurs again soon.

Load All fields when loading data.
An error occurs from the Query configuration stage.

I would appreciate it if you could let me know the cause of the error and how to resolve it.

Hi @banapresso

Are you able to query that table with curl or postman? Is the plugin set up properly?

Thank you for leaving a reply.

Queries using curl or postman work normally.

It works well in a deployment environment, but the above error occurs in an editing environment.

I think this is more of a front-end error. Not a network issue. It seems like the supabase instance is not present (null) at the moment of the execution - judging from the message, but I might be wrong.

1 Like

@banapresso Are you getting this error with all collections/tables or just one specific table?

Getting this in multiple collections. Have to refresh the page multiple times.

Sometimes, the plugin clears the table selection, and I must click the refresh icon in the collection settings.

Most of my roadblocks with Supabase are usually RLS based. Especially if you’re using Joins, FK’s with multiple tables as correct RLS needs to be setup across all tables.

Are you using Authentication in some way? Occurs “soon” again could be related to a session issue. Is a action or variable restricted behind that which is getting blocked? Because you’ve got a “null” value, there’s data missing.

It it works in prod and not editior, have you tried checking and comparing the network requests in the browser inspect tool? I find that really useful and only recently realised how useful it is as there can be ambiguity with filters and seeing the actual query weweb fires off helps debugging.

Yup! I love Supabase’s easy way to impersonate a user. I have multiple personas so when I have an issue with the backend, my first test is to go to the CLI and impersonate that specific user.

Hi, did you get it fix? i have the same issue.

1 Like

Hi everyone, we have seen reports regarding this issue. We are not quite sure yet why it happens, but it looks like a temporary issue. Reconnecting your Supabase account to the plugin settings seems to fix it. Let me know if you are still stuck! Thanks

I wanted to mention that I’ve seen this popup two or three times. I believe I either reloaded the page or it connected after a few seconds.