SupabaseS
Supabase•4y ago
galizar

Basic query works in V1 but not in V2

I am trying to migrate to V2 and I realized the queries were not working at all with V2, so I set up this two test functions:

V1: 
type group = Database['public']['Tables']['groups']['Row'];

const supabase = createClient(url, anonKey);

const propColumns = 'name, isTrashed:is_trashed';

(async () => {
    await supabase.auth.signIn({email, password});

    const props = 
        await supabase
            .from<group>('groups')
            .select(propColumns);

    console.log(props);

})();


V2:
const supabase = createClient<Database>(url, anonKey);

const propColumns = 'name, isTrashed:is_trashed';

(async () => {
    await supabase.auth.signInWithPassword({email, password});

    const props = 
        await supabase
            .from('groups')
            .select(propColumns);

    console.log(props);
})();


And indeed, the V1 version works as expected, but the V2 one does not return the correct data, it's undefined

I've taken a look at the logs in the app page and there's this key difference in there:

V1:
  "sb": [
    {
      "auth_user": "e92a8280-9d20-4dd9-9c0f-40c441810c41"
    }
  ],
  "search": "?select=name%2CisTrashed%3Ais_trashed",
  "url": "https://app url/rest/v1/groups?select=name%2CisTrashed%3Ais_trashed"


V2:
  "sb": [],
  "search": "?select=name%2CisTrashed%3Ais_trashed",
  "url": "https://app url/rest/v1/groups?select=name%2CisTrashed%3Ais_trashed"


It seems like the client isn't authenticated with V2, so RLS is doing its job. Is there something I'm missing regarding signInWithPassword? The way it is talked about in the release notes sounds like it should be a swap in replacement and a quick look at the source seems to confirm that it does basically the same thing as v1's signIn . Would greatly appreciate any pointers
Was this page helpful?