PhoneAuth Sign In failure.

[sadiss]

I have Implemented the plugin successfully.

When i add a phone number as test phone in Firebase there is no issue i received verificationID.

but with new number using below code

cfaSignIn('phone', {phone: '+923145225555'}).subscribe( (data) => {
      console.log(data);
    }, (err) => {
      console.log('error is below')
      console.log(err);
    });

i am getting error "

rror: PhoneAuth Sign In failure.
    at Object.fromNative (capacitor-runtime.js:226)
    at <anonymous>:1:18

there is not enough detail to debug. Please help me solve this problem.

[hiepxanh]

you can try, using your android studio or xcode to view log

[keyurboss]

If you implementing for IOS then please check #105

[mesqueeb]

I had the same error, but was able to get more information via Android Studio. I found this:

E/Capacitor/Plugin: PhoneAuth Sign In failure. com.google.firebase.auth.FirebaseAuthException: This app is not authorized to use Firebase Authentication. Please verify that the correct package name and SHA-1 are configured in the Firebase Console. [ App validation failed ]

[keyurboss]

@mesqueeb Please check in firebase console Select your Project and in project setting Select your app In this case Android Then under that there will be list of finger prints or sha1 hashes....

So add you debugging app hash...

You will be good to go

[keyurboss]

@mesqueeb Please check in firebase console Select your Project and in project setting Select your app In this case Android Then under that there will be list of finger prints or sha1 hashes....

So add you debugging app hash...

You will be good to go https://support.google.com/firebase/answer/9137403?hl=en

[mesqueeb]

@rpsoftech Thanks! I was able to get it to work by adding 3 sets of SHA-1 + SHA-256 keys. (6 keys in total)

One set is from the local debug keystore which is added by Android Studio I think:

keytool -list -v \
-alias androiddebugkey -keystore ~/.android/debug.keystore

Other 2 sets are from the "Google Play Console" if you go to "Signing" you can find your "upload" keys and your "release" keys.

I don't know 100% sure if I need all of these 3 sets, but I just added them all to the Firebase console to be sure (total of 6 keys.)

[keyurboss]

@mesqueeb

@rpsoftech Thanks! I was able to get it to work by adding 3 sets of SHA-1 + SHA-256 keys. (6 keys in total)

One set is from the local debug keystore which is added by Android Studio I think:

keytool -list -v \
-alias androiddebugkey -keystore ~/.android/debug.keystore

Other 2 sets are from the "Google Play Console" if you go to "Signing" you can find your "upload" keys and your "release" keys.

I don't know 100% sure if I need all of these 3 sets, but I just added them all to the Firebase console to be sure (total of 6 keys.)

So Debugging SHA-1 | SHA-256 is needed to be added For Development Production SHA is required IF You Signing It with other Key...

So For Every Signing Key, You need To add SHA To Fire4base console in order to access Firebase...

So For Each Of Your Team Member Using Android Studio on their machine, They Have Their OWN debugging Key...

Here I Would Recommend One thing Use Different Firebase Project For Development and Production .... OR

You Can Use Diffrent App On Same Porject...

Feel Free To Ask Any Question... Thank You

[carlossk]

I solved it with this article for debug and production for Android https://developers.google.com/android/guides/client-auth