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.
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 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