You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the documentation on phone login, Textlocal is listed as a supported provider, with instructions to create API keys via Textlocal signup. However, based on the code, it appears that the implementation is using Textlocal India (api.textlocal.in) rather than the global API (api.txtlocal.com).
The actual Textlocal API seems to be misconfigured or not used correctly in the current implementation. I believe both textlocal.in (India) and textlocal.com (global) should be supported. The documentation is unclear and needs to be more explicit regarding the creation of API keys and which version of Textlocal to use.
Can someone help address this issue?
Thanks
The text was updated successfully, but these errors were encountered:
According to the documentation on phone login, Textlocal is listed as a supported provider, with instructions to create API keys via Textlocal signup. However, based on the code, it appears that the implementation is using Textlocal India (api.textlocal.in) rather than the global API (api.txtlocal.com).
The base URL in the code at this line does not align with the URL documented in the Textlocal OTP API documentation (api.txtlocal.com).
Code used for testing:
const { data, error } = await supabase.auth.signInWithOtp({ phone: "****", });
Error encountered:
{ "session": null, "user": null, "error": "AuthApiError: Error sending confirmation OTP to provider: textlocal error: Invalid login details (code: 3) message" }
The actual Textlocal API seems to be misconfigured or not used correctly in the current implementation. I believe both textlocal.in (India) and textlocal.com (global) should be supported. The documentation is unclear and needs to be more explicit regarding the creation of API keys and which version of Textlocal to use.
Can someone help address this issue?
Thanks
The text was updated successfully, but these errors were encountered: