I have this code here:

js
const { data1, error1 } = await supabase
        .from('activationkeys')
        .select("*")
        .eq('key', body.activationKey)

Used to fetch if there is a key in supabase. No matter what I do, no data is returned at all. Any ideas on when this would happen?

Hello @sticks! This thread has been automatically created from your message in #843999948717555735 a few seconds ago. We have already mentioned the @User role so that they can see your message and help you as soon as possible! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ... menu) and select Leave Thread to unsubscribe from future updates. Want to change the title? Use the /title command! We have solved your problem? Click the button below to archive it.

Well first issue {data1, error1} won't work. you need {data:data1, error:error1} to map the return keys. Next thing to look at would be if you don't meet RLS policy.

sticks (2022-05-03)

Okay. Fixed that issue, but now my signup does not work right?

// Trigger auth signup
    const {user, session, error2} = await supabase.auth.signUp({
        email: body.email,
        password: body.password
    })

No Email, nothing

well at a minimum make error2 error:error2 and see if you have an error

ye should be - seems it's not likeing the password

There is a length requirement I remember, not sure what else.

yeah, was length. Fixed it

Just remember when you use {} you are taking the return object (myObject = await.....) and pulling out of it keys in that object. You can use : to alias the keys.

well it sends you the email saying

Without refreshing my memory, I believe supabase.js will handle the link and use the token in the link to confirm the user on the server and then set the signin event in onAuthStateChange.

so just load the client on your verification page?

Yes, gotrue will look at the url for the info as long as you don't change this default option detectSessionInUrl: true