Firebase is not sending OTP to the Mobile Number

Question

I am facing something different type of problem. I am using Firebase Mobile number authentication in my App. When I am trying to send OTP to the same mobile number that I am using, the OTP is not sending. However, if I am sending OTP to the other mobiles from my mobile OTP is sending. I also found If I send OTP from another mobile to my number OTP is coming. Hence there is no issue of Mobile Number. On Debugging I found that this code block is not working

@Override
    public void onCodeSent(String verificationId, PhoneAuthProvider.ForceResendingToken forceResendingToken) {
        super.onCodeSent(verificationId, forceResendingToken);

        Log.e(TAG, "onCodeSent: s - " + verificationId + " : t - " + forceResendingToken);
        xVerificationId = verificationId;
    }

For other numbers, it is working and verification and forceResendingToken are generating.

score 18 · Answer 1 · answered Feb 06 '19 at 19:01

18

If you have added your phone number in testing under firebase(Sign-in method->Phones). then please remove from there to get otp.

answered Feb 06 '19 at 19:01

Rakesh

522
4
13

2

It is not always the case. I am having these issues with the OTP where some users are not receiving it but some are. – Ashique Bava Oct 08 '21 at 11:23

score 6 · Answer 2 · answered Feb 14 '18 at 07:05

Are you implementing onVerificationCompleted? In the following 2 cases, no OTP is sent, as explained in https://firebase.google.com/docs/auth/android/phone-auth:

Instant verification: phone number can be instantly verified without the need to send an OTP.
Auto-retrieval: Google Play Services can automatically detect the OTP without any user action.

In this case, you will directly get back a PhoneAuthCredential.

score 5 · Answer 3 · answered Mar 21 '20 at 05:55

As explained already, The phone number is getting verified automatically either by

Instant Verification or
Auto Retrieval

which is why onCodeSent() isn't working.

Now, In order to get rid of the problem, you will need to implement onVerificationCompleted(), most chances are that you have implemented it already but you don't know what put inside.

if you are inside onVerificationCompleted(), then you may not have the OTP with you but you definitely have phoneAuthCredential, you just need to pass this variable to mAuth.signInWithCredential() and that should lead to you to your desired output.

sample code for :

        @Override
        public void onVerificationCompleted(@NonNull PhoneAuthCredential phoneAuthCredential) {

            Toast.makeText(getApplicationContext(),"Verifying code Automatically",LENGTH_LONG).show();

            signInWithCredential(phoneAuthCredential);

        }

sample code for :

private void signInWithCredential(PhoneAuthCredential credential) {
    mAuth.signInWithCredential(credential)
            .addOnCompleteListener(this, new OnCompleteListener<AuthResult>() {
                @Override
                public void onComplete(@NonNull Task<AuthResult> task) {
                    if (task.isSuccessful()) {

                        // Sign in success, update UI with the signed-in user's information
                        // Log.d(TAG, "signInWithCredential:success");


                    } else {
                        // Sign in failed, display a message and update the UI
                        // Log.w(TAG, "signInWithCredential:failure", task.getException());

                        }
                    }
                }
            });
}

This was it for me. You too much! I had that onVerificationCompleted method. But I didn't pass the PhoneAuthCredential param. Thanks bro — Uchechukwu Nnabugwu, Mar 06 '21 at 08:11

score 3 · Answer 4 · answered May 14 '20 at 05:57

3

Update the SHA1 fingerprint. It worked for me.

answered May 14 '20 at 05:57

Euclid Stonna

49
6

great, you saved my time. Actually, I forgot to set up the SHA – Vijay Dec 19 '20 at 10:28

Hritik Gupta · Answer 5 · 2020-05-14T09:29:09.060

2

Worked for me .

Sometimes Google is unable to verify the request coming from you app. In order to solve it. Re-generate your app's signing report and get your SHA-1 or SHA-256 fingerprints. Go to your firebase project setting and add those fingerprints.

How to generate fingerprints

edited May 14 '20 at 09:29

answered Mar 30 '20 at 11:44

Hritik Gupta

611
5
20

score 1 · Answer 6 · answered Oct 16 '21 at 04:55

1

In my case, I realized that this problem happens with all numbers that has ported from one provider to another. With phone numbers that has never ported Firebase Authentication works like a charm!

answered Oct 16 '21 at 04:55

Pravin Desai

527
5
18

Did you find any solution for this issue ? I am stuck at this point. – Vishnu E R Jun 14 '22 at 10:10

score 0 · Answer 7 · answered May 23 '20 at 05:45

0

For me application id was not updated since I changed my package name and generated a new google-services.json.

Updating the 'applicationid' solved the issue!

answered May 23 '20 at 05:45

Kanagalingam

2,096
5
23
40

Can you elaborate on what does updating application id mean? – A Yashwanth Mar 28 '21 at 11:49

score 0 · Answer 8 · edited Dec 15 '20 at 17:20

0

Use the dependency implementation 'androidx.browser:browser:1.2.0' in your build.gradle file. Firebase now wants to check verification through images, This dependency will allow to open the browser and the Captcha will be verified and you will get the OTP.

edited Dec 15 '20 at 17:20

Amir Dora.

2,831
4
40
61

answered Dec 15 '20 at 16:46

Abhishek

81
8

score 0 · Answer 9 · answered Sep 09 '21 at 08:53

0

Update your SHA keys. If your app is in Playstore then you will get new SHA keys from Play Console: release---> app intrigity---> SHAH keys. sometimes they updates their website so it will better to search How to get SHA Keys from play console

answered Sep 09 '21 at 08:53

Khurshed Alam

1

1

Please add further details to expand on your answer, such as working code or documentation citations. – Community Sep 09 '21 at 09:13

score 0 · Answer 10 · answered Dec 13 '22 at 12:51

0

In my case, the received OTP was in the spam.

for more information visit

answered Dec 13 '22 at 12:51

Ninad7N

544
4
13

Firebase is not sending OTP to the Mobile Number

10 Answers10

Linked