Phone never set to verified when using Twilio Verify

[NicolasAlmerge]

Bug report

• [x] I confirm this is a bug with Supabase, not with my own application.
• [x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

When the user signs in with their phone with Twilio Verify and confirms their phone number, the phone_verified attribute inside raw_user_meta_data is set to false.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Enable phone authentication with Twilio Verify, enable phone confirmations.
2. Sign in with Twilio Verify and an OTP code.
3. In the auth.users table (and the Supabase dashboard), in the raw_user_meta_data field for that user, we see:

"raw_user_meta_data": {
  "sub": "...",
  "email_verified": false,
  "phone_verified": false
}

Even though we have verified the phone, it sets phone_verified to false.

Expected behavior

We expect phone_verified inside raw_user_meta_data to be true when phone verification was made.

System information

• Version of supabase-swift: 2.24.1

[v-homsi]

Also seeing this issue

[imhxc]

I'm experiencing this issue, it can serious problems.

[ab-elhaddad]

I am facing the same issue, but the phone_confirmed_at is working as expected. You can use it to make your phone verification check.

[abdirahmn1]

+1 am also seeing this issue in my local dev setup and it's driving me crazy 🤒 i also don't understand why such sensitive fields are on user_metadata since these fields can be updated from the client by the user if they are logged in. It doesn't make sense!!

[CristyTarantino]

Is there any update on the issue yet?

[dileeshaupview]

Is there any Fix for this?

[TheOmran]

@kangmingtay @hf any possibility to get some help on this issue? 🙏