signInWithPhoneNumber needs appVerifier: ApplicationVerifier
#8311
Replies: 5 comments 3 replies
-
On top of that,
while on Firebase docs:
for
|
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
also this one: |
Beta Was this translation helpful? Give feedback.
-
Was ripping through as much of this stuff as I could over the weekend, but clearly there's a bit more to do! In general - same as the old namespaced APIs - if there is some area where we are not working like firebase-js-sdk such that we function as a drop-in replacement, the assumption is react-native-firebase is doing it wrong and we have work to do here. So posting up anything you see that we haven't gotten yet is useful and we'll try to correct |
Beta Was this translation helpful? Give feedback.
-
Don't know if this is a types bug but
signInWithPhoneNumber
takes 3 arguments,auth
,phoneNumber
andappVerifier
.According to Firebase docs, we "need" to pass a reCAPTCHA verifier so 2 things are happening:
auth.signInWithPhoneNumber
and just pass 2 params (bye bye modular 😭 )appVerifier
should be removed or be optional.@mikehardy @russellwheatley I believe it's a bug on typings though, let me know if you want me to open an issue:
import { signInWithPhoneNumber} from '@react-native-firebase/auth'
in screenshot below auth is
const auth = getAuth()
Beta Was this translation helpful? Give feedback.
All reactions