This sounds more like an access / auth issue than a connection problem. If Supabase is “connected” but reads return empty and writes don’t persist, it’s usually one of these: \- RLS is enabled but the policy doesn’t match the current user \- the user session isn’t available when the query runs (\`supabase.auth.getUser()\`) \- the table uses a different ID than \`auth.uid()\` (common with profiles) \- or the app is pointing to a different Supabase project than expected A quick test: log the current user ID and compare it with what’s stored in your table. If they don’t match, RLS will return empty every time.