firebase-ios-sdk: 177930107: Dynamic links trowing error

I’ve been having this same issue for weeks as well, and it’s held us from releasing an implementation of DynamicLinks because we also absolutely need NewRelic.

We are using

pod 'Firebase/DynamicLinks', '~> 8.1'
pod 'NewRelicAgent', '7.3.2'

I tried adding the FirebaseDeepLinkAutomaticRetrievalEnabled = NO but even though this did prevent the crash, it also prevented the DynamicLinks from opening.

The solution that worked for us

Believe it or not, placing the NewRelic.start() call at the very top of didFinishLaunchingWithOptions made it work for me. It seems that somehow NewRelic and Firebase are competing for resources and NewRelic being initialized first makes them both work well.

This breaks

FirebaseApp.configure()
NewRelic.start("key")

This works

NewRelic.start("key")
FirebaseApp.configure()

Ironically, the NewRelic setup guide does warn that we absolutely must place their init code in the first line of didFinishLaunchingWithOptions unless we want bad things to happen. Apparently these are the bad things?

If you try this, i’d love to know if it works for you

@nmalancea tagging you because you seem to still be running into this!

Hi Ryan, first of all thank you very much for quick respond.

1 The exact reproducing steps are simple, we used Cocoa to integrate FirebaseDynamicLinks, right after it we press on RUN and it shows Thread and Crashing, project cannot proceed at this step.

2 This happening right in the Xcode with connected Simulator Device and Real Phone, both cases are showing this thread.

Additional info: We’ve found out other people have this problem also, and we found out that if we disable FirebaseDeepLinkAutomaticRetrievalEnabled with a value NO to the Info.plist the error is disappearing, unfortunately the whole feature stops working. The link for this method is https://github.com/firebase/firebase-ios-sdk/issues/4308

Screenshot:

3 We would like to know for which features FirebaseDeepLinkAutomaticRetrievalEnabled is responsible exactly, it seems after we disable it it do not pass any data for Firebase. And there is no any additional information or guide to get whole explanation for this online.

Hope you can help us with this problem, it is very important for us to have this feature in our application.

Just to share that I had the same issue/crash when adding the Firebase/DynamicLinks through Cocoapods, and the above suggestion about initialising the NewRelic Before Firebase fixes the issue 🤷‍♂️

I have a similar issue, same kind of exception but on the line 79 _wkWebView = [[WKWebView alloc] init]; of the file FIRDLJavaScriptExecutor.m.

This issue only happens when I compile with Xcode 12 for an iOS 11.X simulator. It works properly with an iOS 14.X simulator.

@VladislavShergin are you using an M1 mac ? Just tried on an Intel based mac and can’t seem to reproduce.

Dear Ryan, we also have additional question.

The main reason we’ve integrated Google Dynamic links is to get Source/Medium for tracking orders through the dynamic link. We would like to saw conversion of each order with Source/Medium in Google Analytics associated project. The project is directly connected to ur Firebase.

We’ve integrated Dynamic links in Android and it works perfectly, example screenshot: And for the IOS we did the same, but data of the source and medium is not showing in any case, example screenshot: As you can see from a screenshot for IOS, and as a result the source showing as (direct), we’ve followed all procedure explained on official site and youtube guide.

Our main goal is not to resolve a Thread for SDK, but to have the main source and medium regarding to the order in GA - conversions.

Please tell us is there any way to check or trace the medium/source for dynamic links or is there is something what we did wrong while implementing the feature.

Thank you.