FirebaseApp.configure() conflicts with other frameworks (Facebook Login)

[firebase]

FirebaseApp.configure() conflicts with other frameworks (Facebook Login)

[chetandobariya]

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 FirebaseAppDelegateProxyEnabled set to NO in your app's info.plist

[paulb777]

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.

[rockbruno]

Hey there,
I just updated it, but unfortunately the problem still happens 😢

[paulb777]

Thanks for checking. We'll look deeper.

[morganchen12]

@rockbruno are you getting any errors in console when this happens? Can you upload a sample that reproduces this issue?

[bruno-rocha-movile]

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):
<Debug> [Firebase/Analytics][I-ACS023000] Deep Link Web URL query is empty

We were able to overcome it by adding FirebaseAppDelegateProxyEnabled = NO to our Info.plist, although that most likely disables half of Firebase. Since we just needed the analytics portion, it was good enough for us.

Will make a sample

[baolocdo]

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?
The debug log is basically that Analytics is trying to get the utm_ params from the URL to log campaign events. It seems that the AppDelegateProxy does swizzling correctly.
It's ok if you turn off the feature and follow the instructions in FIRAnalytics+AppDelegate.h to avoid missing campaign events.
It would be nice to solve the right problem.

[paulb777]

Closing due to inactivity. Please reopen if there is still an issue.