Closed malikoum94 closed 6 years ago
@malikoum94 thanks for reporting, I can see what the issue is so will get a patch version out today for this. Issue also applies to confirmPasswordReset as well as the 2 methods you mentioned above.
@malikoum94 As an aside, what is your use case for applyActionCode
or checkActionCode
? I've not come across why these might be used before and just wanted to check that you're not just trying to log the user in? If you are then there is now a verifyPhoneNumber
example on the docs:
https://rnfirebase.io/docs/v3.1.*/auth/phone-auth#verifyPhoneNumber
Hi guys,
@Salakar thanks it will be appreciate!
@chrisbianca my use case is not to log in the user just verify his phone so on iOS i can't verify is phone number because the event of verifyPhoneNumber
send null
for the code. For log in the user i use signInWithPhoneNumber
but i have to add some number on one account so i just need to log in with one and for other phone just verify.
This was fixed as part of v3.1.1
Issue
Hi,
I try to use
firebase.auth(). verifyPhoneNumber (phoneNumber)
and afterfirebase.auth(). applyActionCode (code)
orfirebase.auth(). checkActionCode (code)
but both aren't working and all other function work good!firebase.auth(). verifyPhoneNumber (phoneNumber)
return this, but send the code:{ verificationId: a big hash string, code: null, error: null, state: 'sent' }
firebase.auth(). applyActionCode (code)
andfirebase.auth(). checkActionCode (code)
always return this:And my code look like this:
My Podfile:
My app/build.gradle:
This issue is on both OS and can't avoid this, have you any solution?
Thanks
Environment