Be able to store phone number without SMS provider

The problem


When calling supabase.auth.updateUser({ phone }) to save a phone number for regulatory (KYC) and security purposes, the request fails with the following error: Unable to get SMS provider
This happens even though we are not using phone-based login or verification.

We are building regulated services and need to store phone numbers securely for compliance. The fact that updating the phone field in auth.users requires an active SMS provider—even when not using SMS features—is unexpected and limiting.

This behavior forces us to duplicate the phone number field in a custom profiles table, leading to fragmented data — even though the phone number is logically tied to the user's identity.


Expected behavior


It should be possible to store a phone number in a user’s profile (e.g., for KYC or internal security purposes) without requiring an SMS provider