-
Notifications
You must be signed in to change notification settings - Fork 932
signInWithPhoneNumber is not exported in React Native #5638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
same issue |
Same here, we've worked for a week to port the entire app to v9, just to realize at the end when porting |
I confirmed the same problem. undefined is not a function when importing signInWithPhoneNumber |
+1 |
@sam-gc Can we have hot fix for this? This is a critical issue. My project is waiting for it to have new release, we should not hold this CR. |
Same on our end. Spent time porting everything to v9 just to find out phone auth isn’t working. Basically stabding by for a fix |
+1 for this, fresh install of Expo with Firebase, not exported :/ |
+1 here. Can't use v9 |
FYI there is a similar issue for the googleprovider and the email provider . Dead in the water here. Help!!! |
@jbalidiong @sam-gc Please have some response on planning or let us know you're working on it. Besides, You should remove V9 modular on official website if it's not ready yet. Other developers will be affected. |
@innonguyen From what I’ve heard, PhoneAuth is not going to be supported by the new modular SDK (though I hope @Feiyang1 is wrong here). Nor I’ve gotten any reasoning as to why it wouldn’t be supported anymore. That doesn’t explain why some methods from the EmailProvider, so they just might be affectwd by the same issue here. Hoping they’re all supported, since I for one can’t think of an actual limitation .. |
Hi folks, I'm actively working on this, we will export the missing symbols for phone. @sean-m-oleary, what symbol is missing? |
The We're going to export the Phone auth symbols in the RN build so those should be available going forward. |
@sam-gc do we have an ETA for 9.1.4 release date? As for sean’s EmailProvider, I must say it works fine for us, not really sure what his issue is. |
@edi The phone auth symbols and functionality are now exported as of the latest release ( |
I upgraded to 9.2.0 and get error:
I am using the expo provided example. |
@luklew I think this is the same issue as #5688. The ReCaptcha verifier that expo exports will need to be updated to expose a Tagging @byCedric for visibility |
Will that be a quick enough job or should we all downgrade for now? |
@luklew you can work around this by simply adding the following to your code:
|
@luklew Inside the method you're passing phone number the verifier for sending the SMS.
Somewhere before this line, you should add the following:
|
@edi Im getting another error now:
|
A different issue requires a different thread. Also, without an actual snack to check, it's hard to figure out. For me, it works. Open a different thread with all the details, and hopefully others will answer, otherwise, downgrade to 41 / 42 and be done with it. |
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
Steps to reproduce:
It looks like the
signInWithPhoneNumber
and/or other methods and classes likePhoneAuthProvider
are not exported in React Native environments.At Expo, we have a native library to have a working recaptcha (as mentioned in the docs). But without these methods, we won't be able to let people use this way of authentication.
(Disclaimer, I work for Expo)
Relevant Code:
I also made a Snack so you can see the differences between web and android/ios. On web, all 3 types are functions but on android/ios, only the first one is a function.
The text was updated successfully, but these errors were encountered: