-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
FirebaseApp.configure() conflicts with other frameworks (Facebook Login) #80
Comments
Thanks for the bug report. Would you do a pod update to Firebase 4.0.2 and retry? A recent bug fix may address this issue. |
Hey there, |
Thanks for checking. We'll look deeper. |
@rockbruno are you getting any errors in console when this happens? Can you upload a sample that reproduces this issue? |
Hey there, sorry for the delay, I ended up going to a new project. We get a log in the console after attempting to login through Facebook (with Firebase enabled): We were able to overcome it by adding Will make a sample |
Do you have other SDKs (would be great to know the Podfile)? How do you set up your open URL handler(s)? How do you return in those handlers? |
Closing due to inactivity. Please reopen if there is still an issue. |
After spending an almost full day, I have figure out the problem. Below solution works like charm! You can prevent Firebase from swizzling the methods in your AppDelegate by adding |
[READ] Step 1: Are you in the right place?
Yes
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
After running
FirebaseApp.configure()
, other frameworks that rely on url schemes will stop working.Steps to reproduce:
Alternatively
FirebaseApp.configure()
Same problem was reported by someone on stackoverflow. Unfortunately it looks like whatever the configuration method is doing with the original openURL implementation is killing other guys that do the same.
The text was updated successfully, but these errors were encountered: