Can't tell you, but you can typed your request with

from<Type>(...)

hello, does anyone have any react app using github auth via supabase with protected routes that i can refer to or learn from? thank you

Is supabase store move working for you? I always have a 400 error "the resource was not found". Even if I can find the image in the table editor and the storage database

supabase storage 400 error

Hello can someone help me out? I'm running this but i'm not receiving any access token, and i cant figure it out.

js
const {createClient} = require('@supabase/supabase-js')

const supabase= createClient('data,data')

const signIn = async ()=>{
  let {error } = await supabase.auth.signIn({
  phone: 'phone no here',
  
})
if (error){
  console.log(error)
  return
}
}

const verify = async()=>{
  let { session, error } = await supabase.auth.verifyOTP({
  phone: 'phone no here',
  token: 'thetoken'
  
})

}

verify()

bump. I have the same question 🙂

you can sign in your users with specific scopes. The information is here in the doc: https://supabase.com/docs/reference/javascript/auth-signin#sign-in-with-scopes

Ah excellent, thanks!

Hey folks, I've been having a great time using Supabase but I'm stuck when reading from the database. I'm trying to read a list of e-mail addresses but my console log says; "TypeError: column.split is not a function". Anyone got a clue?

js
testGetEmails: async function () {
      const customersRequestTest = await supabase.from('customers').select(['customer_email_address', 'license_active'])
        if (customersRequestTest.error) throw customersRequestTest.error
        for (const supabaseCustomerTest of customersRequestTest.data) {
          
console.log(supabaseCustomerTest.customer_email_address);
        }
    },

Columns isn't an array, it's a string

@User Thanks! So glad that it's just a minor inconvenience in my code 😅

Hi, apologies for reposting but does anyone have any idea why im not getting the access token?

Me again. I'm trying to get 2 columns from supabase (customer emails & license bool);

js
const customersRequest = await supabase.from('customers').select('customer_email_address', 'license_active')
        if (customersRequest.error) throw customersRequest.error
        await this.sendEmailForm(this.form.userEmailAddress);
        console.log(customersRequest.data.join());
        for (const supabaseCustomer of customersRequest.data) {
          if (supabaseCustomer.license_active == true) {
            await this.sendEmailForm(supabaseCustomer.customer_email_address);
            console.log('kitica' + supabaseCustomer.customer_email_address);
           }
        }

But for some reason, my 'check if license is true' logic isn't working.

'customer_email_address', 'license_active'

should be

'customer_email_address, license_active'

. The first argument of

select

is always a comma-delimited string if you're selecting multiple columns

For those who are using SvelteKit, had problems with RLS on supabase calls in an endpoint? I had to move all supabase calls away from endpoints

Thanks, worked like a charm!

i am facing cross error when update data

I'm trying to update a column with data type JSON, and it's also an array. anybody have any idea why I keep getting the "invalid input syntax for type bytea " error?

Hey peeps! I've been wondering why the Supabase Auth client (or perhaps the GoTrue client used under the hood) doesn't clear the auth data hash upon a successful redirect to a "non-standard" URL, ie. one that doesn't match the default URL's root route. In other words, if I set

redirectTo

to

http://localhost:3000/foobar

, upon successful auth I will be taken to

http://localhost:3000/foobar#access_token=123abc&expires_in=3600&you_get=the_idea

, and that's it, hash will stay there.

Is it possible that

supabase.auth.onAuthStateChange

is broken? The callback I provided is never called, not when I log-in, sign-up or log-out.

Yeah it just seems to flat out not work

Also realtime seems to not work either? I can see in dev tools that I have an open web socket connection and I can see the heartbeats, access tokens and phoenix replies being sent, but the stuff I actually subscribed to does not arrive

Is your RLS working correctly?

I'd hope so the RLS policy for select is just

true

Hmm just the classics. Did you enable replication on the table?

no

i thought it was automatically enabled haha

ty

welp that didn't fix the problem lol - probably just moved it

i had this once where i accidentally had multiple (different) auth instances... played around too much with different initialisation methods