email_confirmed_at is not synced with the auth.users table
Issue - email_confirmed_at is a deciding factor for confirmed_email sign ups. I am facing an issue where the DB data is not in sync with the data returned using the supabase.auth.signUpWith() API.
Expected - Data should be in sync
Actual - Seeing null returned from the API but the DB has a data set to it.
3 Replies
Do mean signInWithPassword?
I get the actual data in the return.
How are you checking the value?
@garyaustin No, supabase.auth.signUpWith() is the API for Kotlin integration.
You should tag Kotlin on your First post.
This is probably because you have email confirm on.
SignUP does not return a valid user session (just some user data) as the user has not confirmed their email yet.
The JS client does not return email_confirmed_at in the case where you are confirming the email as it has not been confirmed yet. I've not tested what happens if you have auto confirm on in the dashboard.