Issue with Appwrite Phone Auth and MSG91 Integration: Missing OTP in SMS

Although the SMS delivery is successful, the OTP (One-Time Password) required for authentication is not included in the message received by the user. This renders the authentication process incomplete and unusable for our intended purposes.

SMS Template: OTP ##var## for ##var##. Please do not share it with anyone. OTP is valid for 5 minutes.

SMS Received by User: OTP for . Please do not share it with anyone. OTP is valid for 5 minutes.

Appwrite Version: 1.5.4

TL;DR

Developers are experiencing an issue with Appwrite Phone Auth and MSG91 integration where the OTP is missing in SMS messages. The problem lies with Appwrite not using the variable in MSG91 to send the SMS API correctly. Attempts to register a new template with the OTP variable failed due to a warning message indicating no variables found in the template. The user is unable to set the ##content## variable in the SMS template despite successful delivery. To fix this issue, the developers need to ensure that the correct variable (##content##) is set in the SMS template for the OTP to be included in the message received by the user.

Would you please set your variable to ##content##?

Okay, I can set ##content## and update you after verifying a new SMS template. it may take some time.

I am unable to set the ##content## variable in the SMS template.

why's that?

Due to TRAI(Telecom Regulatory Authority of India) and DLT rules.

@Steven Is there any other way to resolve this issue?

that doesn't make sense. the only thing you changed in the template is the variable name and that was rejected?

Actually, not rejected. When I'm attempting to register a new template, the platform displays a warning message indicating that no variables were found in the template.