Add new SMS provider Textlocal

[devkiran]

What kind of change does this PR introduce?

Introduce new SMS provider Textlocal (India)

• Close Request to add otp provider for India #308
• Fix added support for textlocal sms provider #305

What is the new behavior?

Change the following env variables, users will be able to send SMS with Textlocal SMS API.

GOTRUE_SMS_TEXTLOCAL_API_KEY=""
GOTRUE_SMS_TEXTLOCAL_SENDER=""

Additional context

Implementation displays the message from Textlocal API if an error occurs.

[kangmingtay]

hey @devkiran & @bhanuc, thanks for getting started with adding this provider and helping us test this out (esp since the supabase team can't test it because we can't create a textlocal account).

Just wanted to check on the phone number format coming from India - we currently assume that all sms providers follow the E.164 format. The other sms providers like twilio, messagebird and vonage all support this format and i was wondering if textlocal supports this format since they don't operate internationally?

[devkiran]

@kangmingtay I have checked their doc, it says mobile numbers in international format (i.e. 918123456789). Here is the send SMS API reference https://api.textlocal.in/docs/sendsms

[kangmingtay]

@devkiran thanks again for iterating on this so quickly! 💯

[github-actions]

🎉 This PR is included in version 2.3.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[bharath2612]

Hey kiran, we are trying to integrate textlocal with supabase for phone otp verification. I have added the api key from textlocal in supabase provider.

This is the error we are getting: AuthException(message: Error sending sms otp: textlocal error: Internal Error, statusCode: 400)

can you guide us here?

[bharath2612]

Hey @devkiran

[kangmingtay]

hey @bharath2612, can you please contact us at support (https://app.supabase.com/support/new) so we can look into your project? you may also want to check your project's auth logs at https://app.supabase.com/project/_/logs/auth-logs which may provide more details on the error you've observed.

[bharath2612]

Hey @kangmingtay, thank you for the revert, we have done some tests and found out that we are receiving the error whenever we use the " {{ .Code }} " in the message. If we replace the .code variable with a 6 digit code, it is sending the otp message succesfully from textlocal.

For example,

What worked for us: "Use OTP 123123 to log into your propzing account. Do not share this OTP."

but when we use this: "use OTP {{ .Code }} to log into your Propzing account. Do not share this OTP." , It throws an error :
AuthException(message: Error sending sms otp: textlocal error: Internal Error, statusCode: 400)

Can you guide us here as to where we are going wrong?

[Sathish-Kumar-A]

Hey @kangmingtay, thank you for the revert, we have done some tests and found out that we are receiving the error whenever we use the " {{ .Code }} " in the message. If we replace the .code variable with a 6 digit code, it is sending the otp message succesfully from textlocal.

For example,

What worked for us: "Use OTP 123123 to log into your propzing account. Do not share this OTP."

but when we use this: "use OTP {{ .Code }} to log into your Propzing account. Do not share this OTP." , It throws an error : AuthException(message: Error sending sms otp: textlocal error: Internal Error, statusCode: 400)

Can you guide us here as to where we are going wrong?

I'm also facing the same issue. got any leads to solve it @bharath2612 ?

[vasanth-ravisankar]

It seems there is another PR regarding TextLocal integration. #853. It mentions that the TextLocal endpoint has been changed and it is getting fixed through that PR. But it has been closed without any further updates. And the AuthException(message: Error sending sms otp: textlocal error: Internal Error, statusCode: 400) is still persisting with TextLocal. Is there any update on this front? @devkiran @kangmingtay

[askYourTask]

yes, i too face the same issue, it still says AuthException(message: Error sending sms otp: textlocal error: Internal Error, statusCode: 400)

[Sathish-Kumar-A]

I think the problem is due to SMS template configuration from operator in Textlocal. you have to create a customized SMS template from the operator e.g. Airtel, Vodafone (India). Then configure this template in the text local with the header ID. After this process, It may work.