I'm having the same issue, in addition, I'm not using a custom domain and in android works correctly.

+1.

To work around this issue I'm using Linking package from RN:

   if (Platform.OS === 'ios') {
      url = await Linking.getInitialURL();
    } else {
      const res = await dynamicLinks().getInitialLink();
      if (res) {
        url = res.url;
      }
    }

@TalEliel @MarcoF09 @ahanusek
Hey! I'm having similar issues as well. Where did you guys find information about configuring AppDelegate.m to allow dynamic links to work (back/foreground)?

I spent a day looking for those without luck. And it seems what needs to be added to AppDelegate.m on v5 is different from v6... right?

I appreciate in advance if you guys could point me to some documentation about that.

I'm in the same boat, why do the v6 docs not cover the necessary configurations for RNFB Dynamic Links in the AppDelegate.m?

Here's a snippet of what I found, but it only sometimes works:

AppDelegate.m

- (BOOL)application:(UIApplication *)application openURL:(NSURL *)url
  sourceApplication:(NSString *)sourceApplication annotation:(id)annotation
{
  return [RCTLinkingManager application:application openURL:url
                      sourceApplication:sourceApplication annotation:annotation];
}

- (BOOL)application:(UIApplication *)application
            openURL:(NSURL *)url
            options:(NSDictionary<NSString *, id> *)options {
    return [[RNFBDynamicLinksAppDelegateInterceptor sharedInstance] application:application openURL:url options:options];
}

- (BOOL)application:(UIApplication *)application
continueUserActivity:(NSUserActivity *)userActivity
 restorationHandler:(void (^)(NSArray *))restorationHandler {
     return [[RNFBDynamicLinksAppDelegateInterceptor sharedInstance] application:application continueUserActivity:userActivity restorationHandler:restorationHandler];
}

I try to handle a login link for sendSignInLinkToEmail in my Login component:

useEffect(() => {
    return dynamicLinks().onLink(async link => {
      if (auth().isSignInWithEmailLink(link.url)) {
        if (!email) {
          // TODO: If no email, have user input
          return
        }

        try {
          await auth().signInWithEmailLink(email, link.url)
        } catch (e) {
          console.error(e)
        }
      } else {
        // Not a dynamic link for auth, handle with router
      }
    })
  }, [email])

The issue this only sometimes gets triggered. I can't figure out why, maybe it's a dev only thing, but it's frustrating that the docs don't clearly say what the setup ought to be so I can troubleshoot just my code instead

PRs always welcome, the docs all have an edit button at top right

@russellwheatley only a comment, in my case occurs also in version 5.6.0.

I am having the same issue, someone can address this issue?

Hey @TalEliel, could you please confirm that you have actually added a URL type? Effectively, you need to add your Bundle ID to the URL Schemes property, and call the Identifier property whatever name you want (I've called mine "Bundle ID").

If I did not set this, then the returned object from the dynamicLinks().getInitialLink() call would be null.

Hey @russellwheatley , yes i did add a utl type with the bundle identifie.
I just believe that there shoulb be some code to be implemented in the appDelegate.m file that is nowehre to be found in the documentaion and every code snipet i found online didn't work either

Interesting. I created a fresh RN project, the only code I added to my appDelegate.m was the Firebase Config code you already have in your appDelegate.m:

Do you mind if I see your GoogleServices-info.plist, please @TalEliel ?

@russellwheatley sure. this is the file.
and the strings are the actual data i replaced them for privacy

do you mind pasting that into the comment box, please?

@russellwheatley

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd%22%3E
<plist version="1.0">
<dict>
    <key>CLIENT_ID</key>
    <string>CLIENT_ID</string>
    <key>REVERSED_CLIENT_ID</key>
    <string>REVERSED_CLIENT_ID</string>
    <key>API_KEY</key>
    <string>API_KEY</string>
    <key>GCM_SENDER_ID</key>
    <string>GCM_SENDER_ID</string>
    <key>PLIST_VERSION</key>
    <string>PLIST_VERSION</string>
    <key>BUNDLE_ID</key>
    <string>BUNDLE_IDr</string>
    <key>PROJECT_ID</key>
    <string>PROJECT_ID</string>
    <key>STORAGE_BUCKET</key>
    <string>STORAGE_BUCKET</string>
    <key>IS_ADS_ENABLED</key>
    <false></false>
    <key>IS_ANALYTICS_ENABLED</key>
    <false></false>
    <key>IS_APPINVITE_ENABLED</key>
    <true></true>
    <key>IS_GCM_ENABLED</key>
    <true></true>
    <key>IS_SIGNIN_ENABLED</key>
    <true></true>
    <key>GOOGLE_APP_ID</key>
    <string>GOOGLE_APP_ID</string>
    <key>DATABASE_URL</key>
    <string>DATABASE_URL</string>
</dict>
</plist>

Hmmm, there is nothing out of the ordinary with your GoogleServices-info.plist. Unfortunately, I cannot debug if I cannot recreate. Do you mind creating a reproduction repository of this issue, please?

I'm also having problems with Dynamic Links on iOS. Both onLink and getInitialLink return null.
I can see in XCode debug console:

2020-04-23 16:11:08.614347+0200 App[52231:1275885] Task <3E55F296-87F6-43FE-BB40-46314F6FF585>.<5> finished with error [-1003] Error Domain=NSURLErrorDomain Code=-1003 "A server with the specified hostname could not be found." UserInfo={NSUnderlyingError=0x600001d29650 {Error Domain=kCFErrorDomainCFNetwork Code=-1003 "(null)" UserInfo={_kCFStreamErrorCodeKey=8, _kCFStreamErrorDomainKey=12}}, NSErrorFailingURLStringKey=https://firebasedynamiclinks-ipv6.googleapis.com/v1/installAttribution?key=<some_key>, NSErrorFailingURLKey=https://firebasedynamiclinks-ipv6.googleapis.com/v1/installAttribution?key=<some_key>, _kCFStreamErrorDomainKey=12, _kCFStreamErrorCodeKey=8, NSLocalizedDescription=A server with the specified hostname could not be found.}

Not sure if this is related? I see a similar report in firebase-ios-sdk

The same issue with me. Is there any update for this?

same problem.

Same issue. I was able to see the link with using React Native's Linking module, however it only interprets shortened URL's via the "Open link in app?" interstitial. Clicking the link from my Messages app outputs only the already shortened URL.

Also seeing this issue here, could it be related?

facebook/react-native#24429

I had the same issue initially.
For me getInitialLink also sometimes did return null but then onLink returns the correct data.
This is my implementation if anybody wants to try it (top of App.js):

import { useEffect } from 'react';
import dynamicLinks from '@react-native-firebase/dynamic-links';

const useSetupDynamicLinks = () => {
  const handleDynamicLink = async (link) => {
    if (link && link.url) {
      // do something with it
    }
  };

  useEffect(() => {
    // for background/quit events
    const link = dynamicLinks().getInitialLink();
    handleDynamicLink(link);

    // for foreground events
    const unsubscribeLinkListener = dynamicLinks().onLink(handleDynamicLink);
    return () => unsubscribeLinkListener();
  }, []);
};

export default useSetupDynamicLinks;

Hey @bobinrinder
Thanks for sharing that! Do you mind sharing also what you have in your AppDelegate.m?

GULAppDelegateSwizzler seems to call RNFBDynamicLinksAppDelegateInterceptor with nil values.

So

- (BOOL)application:(UIApplication *)application
            openURL:(NSURL *)url
  sourceApplication:(NSString *)sourceApplication
         annotation:(id)annotation

openURL is nil, initialLinkUrl is not setup and remains nil/null.

I'm seeing this behavior on my app as well. Any additional context that would be helpful?

My issues appeared to be related to using a custom domain and needing to set FirebaseDynamicLinksCustomDomains as documented in the official FB docs: https://firebase.google.com/docs/dynamic-links/ios/receive#objective-c_3

EDIT: Scratch that... it was working in my Debug build but doesn't work on a cold app-start in my release version

Background

I'm experiencing this issue too. Specifically, the Dynamic Link from a "passwordless email authentication" email, when clicked in Apple Mail, has failed to open my app, and has instead opened iOS Safari. This has been the case for 3 out of my 8 testers, which is a really awful failure rate. They're all on iOS 13.

@russellwheatley Could I please have a basic sanity check of whether my AppDelegate.m has been implemented correctly to expect that Dynamic Links should work?

I've following the latest Dynamic Links documentation for React Native Firebase (which, incidentally, have greatly improved in the last weeks – thank you!). It doesn't mention anything about how we should set up AppDelegate.m, however.

Firebase Dynamic Links for iOS official docs

For reference (please nobody copy this without reading on), in Google's Firebase Dynamic Links docs for iOS, they show the following:

- (BOOL)application:(UIApplication *)app
            openURL:(NSURL *)url
            options:(NSDictionary<NSString *, id> *)options {
  return [self application:app
                   openURL:url
         sourceApplication:options[UIApplicationOpenURLOptionsSourceApplicationKey]
                annotation:options[UIApplicationOpenURLOptionsAnnotationKey]];
}

- (BOOL)application:(UIApplication *)application
            openURL:(NSURL *)url
  sourceApplication:(NSString *)sourceApplication
         annotation:(id)annotation {
  FIRDynamicLink *dynamicLink = [[FIRDynamicLinks dynamicLinks] dynamicLinkFromCustomSchemeURL:url];

  if (dynamicLink) {
    if (dynamicLink.url) {
      // Handle the deep link. For example, show the deep-linked content,
      // apply a promotional offer to the user's account or show customized onboarding view.
      // ...
    } else {
      // Dynamic link has empty deep link. This situation will happens if
      // Firebase Dynamic Links iOS SDK tried to retrieve pending dynamic link,
      // but pending link is not available for this device/App combination.
      // At this point you may display default onboarding view.
    }
    return YES;
  }
  return NO;
}

React Native Dynamic Links

I notice that in React Native Firebase, however, some magic is going on. The library implements RNFBDynamicLinksAppDelegateInterceptor, which swizzles the app's AppDelegate.

I have no clue exactly what the swizzling is doing behind the scenes, and it would be great if it were documented!

My own code

My guess from debugging, though, is that RNFBDynamicLinksAppDelegateInterceptor runs before our own AppDelegate runs, and therefore when using React Native Firebase, we don't need to write anything in openURL:options:completionHandler: at all.

Nonetheless, I've put a guard in to make sure that my app (which also handles URLs passed to it from an Action Extension) doesn't accidentally handle a URL that has already been handled. Could you please clarify whether this guard is redundant @russellwheatley.

openURL:options:completionHandler:

// For an app called Sundial, with the bundle ID: "com.sundial.app"
- (BOOL)application:(UIApplication *)app openURL:(NSURL *)url options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options {
  if(url){
    if([url.absoluteString hasPrefix:@"com.sundial.app://google"]){
      RCTLogInfo(@"This is a Firebase Dynamic Link! Should have been handled by RNFBDynamicLinksAppDelegateInterceptor already.");
      return YES;
    }

    if([url.absoluteString hasPrefix:@"com.sundial.app://sundial/openURL/"]){
      RCTLogInfo(@"Our Action Extension (e.g. 'Open in Sundial') passed us a link! TODO: handle.");
      return YES;
    }
  }
  return NO;
}

application:didFinishLaunchingWithOptions:

For my application:didFinishLaunchingWithOptions:, I've written the following:

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  // As per: https://rnfirebase.io/#configure-firebase-with-ios-credentials
  if ([FIRApp defaultApp] == nil) {
    [FIRApp configure];
  }

 // Strictly set up RCTBridge, etc. only AFTER configuring FIRApp!

  // ...

  // I was advised from somewhere to add in this line, possibly from the React Native
  // Firebase Issues. Or maybe it was recommended by some other unrelated library.
  // I've long since forgotten.
  //
  // Either way, could you please clarify whether this line should be removed or not,
  // given that React Native Firebase has this mysterious AppDelegate swizzling?
  [super application:application didFinishLaunchingWithOptions:launchOptions];

  return YES;
}

Thank you very much for any help! Happy to provide more details.

+1.

To work around this issue I'm using Linking package from RN:

   if (Platform.OS === 'ios') {
      url = await Linking.getInitialURL();
    } else {
      const res = await dynamicLinks().getInitialLink();
      if (res) {
        url = res.url;
      }
    }

@ahanusek Do the Dynamic links work for iOS in all cases when you use Linking, where they'd been failing before by using React Native Firebase Dynamic Links?

Has anyone faced the issues when it says:

NSErrorFailingURLStringKey=https://firebasedynamiclinks-ipv6.googleapis.com/v1/installAttribution?key=AIzaSyC4MXdWE2_EwJQXU1kC8hZZ7Vm1XOvCufA,
NSErrorFailingURLKey=https://firebasedynamiclinks-ipv6.googleapis.com/v1/installAttribution?key=AIzaSyC4MXdWE2_EwJQXU1kC8hZZ7Vm1XOvCufA

The whole error:

Task <401C75F4-F8F0-47F4-A92D-7778E3F49A72>.
<5> finished with error [-1003]
Error Domain=NSURLErrorDomain Code=-1003
"A server with the specified hostname could not be found."
UserInfo={NSUnderlyingError=0x600002cdc420
{Error Domain=kCFErrorDomainCFNetwork Code=-1003 "(null)"
UserInfo={
_kCFStreamErrorCodeKey=8,
_kCFStreamErrorDomainKey=12}},
NSErrorFailingURLStringKey=https://firebasedynamiclinks-ipv6.googleapis.com/v1/installAttribution?key=AIzaSyC4MXdWE2_EwJQXU1kC8hZZ7Vm1XOvCufA,
NSErrorFailingURLKey=https://firebasedynamiclinks-ipv6.googleapis.com/v1/installAttribution?key=AIzaSyC4MXdWE2_EwJQXU1kC8hZZ7Vm1XOvCufA,
_kCFStreamErrorDomainKey=12,
_kCFStreamErrorCodeKey=8,
NSLocalizedDescription=A server with the specified hostname could not be found.}

🙏

@alex-mironov if I recall correctly someone mentioned it in another issue and it was their project setup was incomplete. #3755 (comment)

@mikehardy thanks, from what I can tell setup is fine, the link is opened. The problem I'm seeing, is that this failure on start increases startup time significantly. I'm trying to find a way to postpone deeplinks initialization, but it seems to be native part, which I cannot influence much from the JS...

Here is related issue btw firebase/firebase-ios-sdk#5032

How unfortunate. A quick read of that issue (thanks for the link!) shows this as prior art: googleapis/google-api-dotnet-client#1186 (comment) and indicating that the hostname is either misconfigured or as a recent PR indicates, they need to handle it better

In the meantime, there is nothing as nifty that I have seen as patch-package for cocoapods, but I wonder if you could hand-hack https://github.com/firebase/firebase-ios-sdk/blob/master/FirebaseDynamicLinks/Sources/FIRDynamicLinkNetworking.m#L36 to be v4 in both cases if it would work 🤔 for now

So after reading the entire thread we're still nowhere near to understanding what configuration is actually required for AppDelegate.m. All I can say for certain is that in a completely fresh project, the current docs for Dynamic Links at rnfirebase.io are inconclusive and do not trigger events when links are opened.

Hitting this issue also on iOS. Followed the guide here https://rnfirebase.io/dynamic-links/usage#listening-for-dynamic-links. App opens correctly when clicking on the dynamic link but dynamicLinks().getInitialLink() and dynamicLinks().onLink() aren't working?

Oh apologies, it seems like its actually an issue with the firebase sdk itself (as mentioned by others above). firebase/firebase-ios-sdk#5032

Check Xcode and I'm getting the same error:

Task <0B09E54B-6A0D-46EF-8410-2DE8B08B2313>.<3> finished with error [-1003] Error Domain=NSURLErrorDomain Code=-1003 "A server with the specified hostname could not be found." UserInfo={NSUnderlyingError=0x282c99ce0 {Error Domain=kCFErrorDomainCFNetwork Code=-1003 "(null)" UserInfo={_kCFStreamErrorCodeKey=8, _kCFStreamErrorDomainKey=12}}, NSErrorFailingURLStringKey=https://firebasedynamiclinks-ipv6.googleapis.com/v1/installAttribution?key=AIzaSyAlb7tK2gxW34JefQLI7uEm5j22ICCiILk, NSErrorFailingURLKey=https://firebasedynamiclinks-ipv6.googleapis.com/v1/installAttribution?key=AIzaSyAlb7tK2gxW34JefQLI7uEm5j22ICCiILk, _kCFStreamErrorDomainKey=12, _kCFStreamErrorCodeKey=8, NSLocalizedDescription=A server with the specified hostname could not be found.}

@mrbrentkelly reach right into that cocoapod and hack out the ipv6 thing. I bet it works for you. If it does, then I would write a tiny idempotent change in ruby in your podfile as a post_install hook https://guides.cocoapods.org/syntax/podfile.html#post_install

That hook should take the patch you generate from running patch after making your change, and should attempt to apply it (a la the javascript-level patch-package)

You'll have reproducibly applied your change then and you can maybe move forward until the upstream issue is resolved

There are many in this position, any report you had of success with this style would probably be met with a lot of thanks

Thanks @mikehardy 👍. I just removed what I thought to be the code ipv6 code in FirebaseDynamicLinks Pod. The error goes away from the console but dynamicLinks().getInitialLink() and dynamicLinks().onLink() still aren't getting called unfortunately 🤔

Ok I've managed to get this working by simply adding FirebaseDynamicLinksCustomDomains to my Info.plist (as suggested by others above 👍).

Works on Debug and Release builds thankfully.

https://firebase.google.com/docs/dynamic-links/ios/receive#open-dynamic-links-in-your-app

<key>FirebaseDynamicLinksCustomDomains</key>
<array>
  <string>https://mycustomdomain.com/</string>
</array>

Note, I'm still seeing the "A server with the specified hostname could not be found." error in my Xcode console but it doesn't appear to affect the dynamic link going through.

@mrbrentkelly I had a similar experience to you where adding the plist key/value let my links staart working as expected. However I quickly realized that the flow was pretty flaky. I would say I had about 50/50 success/failure when using the link through an app install

I fixed with this simple line in the openURL delegate in AppDelegate.m:
[[FIRDynamicLinks dynamicLinks] dynamicLinkFromCustomSchemeURL:url];

And my final code with Firebase Dynamic Links + React Native Linking:

- (BOOL)application:(UIApplication *)app openURL:(NSURL *)url options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options
{
  // fix Firebase Dynamic Links
  [[FIRDynamicLinks dynamicLinks] dynamicLinkFromCustomSchemeURL:url];

  // Deep Links required: https://reactnative.dev/docs/linking#enabling-deep-links
  return [RCTLinkingManager application:app openURL:url options:options];
}

- (BOOL)application:(UIApplication *)application continueUserActivity:(nonnull NSUserActivity *)userActivity restorationHandler:(nonnull void (^)(NSArray<id<UIUserActivityRestoring>> * _Nullable))restorationHandler
{
  // Deep Links required: https://reactnative.dev/docs/linking#enabling-deep-links
  return [RCTLinkingManager application:application continueUserActivity:userActivity restorationHandler:restorationHandler];
}

Versions:

react-native: 0.61.5
@react-native-firebase/dynamic-links: 7.2.0

@RodolfoGS something went wrong with AppDelegate swizzling for you, that should not be necessary and is not documented because it is not supposed to be necessary:

Haven't had problems with current lib version, except with Detox e2e tests using device.openURL().
@RodolfoGS 's snippet fixed it for me.

I thought RCTLinkingManager implementation was not needed when using Firebase Dynamic Links, but apparently it is?

I was getting very inconsistent results when I set up the onLink listener before calling getInitialLink. Sometimes it would trigger the listener first and getInitialLink would be null. YMMV.

Now considering just using the standard React Native Linking lib with Linking.getInitialURL() and Linking.addEventListener('url', handler) combined with the new dynamicLinks.resolveLink() to get the best of both worlds. Will I miss anything from the Dynamic Links counterparts?

Hey guys, I really don't know if it matters or not but have you tried setting FIROptions before FIRApp configure like so:

[FIROptions defaultOptions].deepLinkURLScheme = @"deep_link_alias_name_or_whatever";
[FIRApp configure];

ps. I'm using v5.6.0

from google docs you need to add that FirebaseDynamicLinksCustomDomains in info.plist .
iOS only: In your Xcode project's Info.plist file, create a key called FirebaseDynamicLinksCustomDomains and set it to your app's Dynamic Links URL prefixes. For example:

<key>FirebaseDynamicLinksCustomDomains</key>
<array>
  <string>https://example.com/link</string>
  <string>https://example.com/promos</string>
</array>

https://firebase.google.com/docs/dynamic-links/custom-domains#using_your_web_domain_for