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
I am now able to send otp on mobile data. I had forgot to put android:usesCleartextTraffic="true"
But now my problem is this:
I have implemented otp on this class
public class Otp_varificaion extends AppCompatActivity implements VerificationListener{
}
This does not extend application. My application class is different.
Now if i use autoverification
.setAutoVerification(Otp_varificaion.this)
then i get logged in but also i get error code. Also my OTP message has gibberish is i use autoverification
Hello @cooler1234
May you please share your code snippet or share the error code and OTP message you are getting.
That will really help us to understand the issue and fix it.
Also, if you share your application class code and SDK version too, which you are using in your app.
Thank you for your patience!
When i try to send otp on mobile data, it does not work, but it works on wifi.
Second problem is on mobile data If i press resend, it gives error code 38
On wifi i tried to log the code and message inside run method, here is what i got
2020-10-03 15:04:05.223 4281-4281/com.management.anmolcoal E/otpresonsemsg91: onSendOtpResponse: 32=======306a636f6466383039363536
2020-10-03 15:04:07.843 4281-4281/com.management.anmolcoal E/otpresonsemsg91: onSendOtpResponse: 20=======250282
2020-10-03 15:04:08.426 4281-4281/com.management.anmolcoal E/otpresonsemsg91: onSendOtpResponse: 35=======otp_verified
2020-10-03 15:04:08.462 4281-4281/com.management.anmolcoal E/otpresonsemsg91: onSendOtpResponse: 44=======already_verified
Even when the number is verified its still calling onSendOtpResponse and then it gives an error message.
i am using lib 1.3.8
Also on wifi the OTP message i receive has a gibberish line after the OTP.
"Your Coalmantra Verification OTP is 22222. g5uzpW9Rs0v
The text was updated successfully, but these errors were encountered: