Thanks @jibin2706! Going to close for now but let us know if there are any further issues.

working now @J0 I was using auth.admin.createUser instead of supabase.auth.signInWithOtp

HI all!

I found something that might help the debugging of this problem.

TL;DR

It seems the Supabase-CLI is reading config.toml OK but when it creates the envs that Gotrue will use later, it messes the expected format.

Maybe changing the method used to generate the value for GOTRUE_SMS_TEST_OTP should be implemented.

On the CLI side

If we see line 421 of start.go, the value for that env being produced by calling testOTP.String(), which produces something like the following: {"7333333333":"123456"}.

Like a total “grug” I’ve done what is in the screenshot bellow to check what is being produced.

The actual output that will be used as env is shown in the screenshot bellow.

On the Gotrue side

Now, on Gotrue, we are using the envconfig package to parse the environments and convert them into the actual types the program expects.

If we add some logs into the conf.LoadGlobal function, we can check what is being produced.

When using GOTRUE_SMS_TEST_OTP={"7333333333":"123456"} we got the following:

When we remove the curly brackets and the double quotes from the env value and pass GOTRUE_SMS_TEST_OTP=7333333333:123456 we got this:

FYI: @J0 & @jibin2706

PS: Sorry for the amount of screenshots, I didn’t find a better way to explain myself.

@jibin2706 do you mind sharing how you’re making the verification? Here’s my setup:

const { data, error } = await supabase.auth.signInWithOtp({
      phone: '12345678'
    })

const res = await supabase.auth.verifyOtp({
		  phone: '12345678',
		  token: '555555',
		  type: 'sms',

    })

and my config.toml contains

[auth.sms.test_otp]
<my_number> = "123456"
12345678 = "555555"

supabase -v gives me 1.112.0

Sorry for the barrage of information - am able to verify with this set up so trying to identify where the issue is coming from

@J0 Using the latest version

@LautaroJayat Thanks so much 🙏 Appreciate your contribution

@jibin2706 we shouldn’t need to change the GoTrue repo I think. Can I check that you’re on the latest version of the CLI?

@LautaroJayat Still getting same error

The env is the following format

GOTRUE_SMS_TEST_OTP=917045386164:123456,917123123232:123456,917213123233:123456

I guess we have to make changes to the gotrue repo as well

@LautaroJayat created a PR for sms template https://github.com/supabase/cli/pull/1655

Thank you! Let me know if you need any assistance there and feel free to tag me for review

Hey team,

Thanks for flagging this! This looks to be an error with how the TEST_OTP config is parsed in the CLI. We’ll look into a fix and get back to you once it’s out.