11

If I install the app when clicking the dynamic link. All of that information from dynamic should be still available when I open the app for the first time.How can I get that information? It is not working when I use this: getInitialLink() returns Promise<string|null>;

ian sembiring
  • 111
  • 1
  • 10
  • I have exactly same issue. Ios work fine. I debugged native java code in firebaselinks.java getInitialLink always return null after installation – 1110 Jul 05 '18 at 14:42
  • Are you just getting back the return value from `getInitialLink()` right away, or do you have an `await` in there? – Todd Kerpelman Jul 09 '18 at 18:20
  • check https://github.com/invertase/react-native-firebase/issues/1273 for reference. – jay shah Jul 10 '18 at 15:00

3 Answers3

1

Since, you haven't mentioned - I'm assuming you are having problems with shorter urls, if that's the case try putting the longer url.

Or refer here on Simon's answer: When I use the long instead of short links, everything works perfectly fine.

On Android, you use the getInvitation() method to get data from the Dynamic Link:

AppInvite.AppInviteApi.getInvitation(mGoogleApiClient, this, false).setResultCallback
(/* ... */);

Then, in the callback, you can get the data passed in the Dynamic Links link parameter by calling the getDeepLink() method:

Firebase Documentation - Use Case

For future reference or detailed answer on Firebase Dynamic Links

Behave just like normal Links

In cases where the application doesn’t require installation (say, if it’s already installed) then clicking the Dynamic Link will automatically open the link to the desired screen.

Dynamic Links have a very simple process flow:

  • The user begins by clicking the Dynamic Link
  • If the the needs of the Dynamic Link target are satisfied (this is, the application being installed) then the user is navigated to the target location
  • Otherwise, if the application requires install in order to navigate to the Dynamic Link target, the the user is taken to the point of install for the application. Once the application has been installed, the user is navigated to the target location of the Dynamic Link

Dynamic Links process flow

And if that wasn’t all, we can integrate Dynamic Links with Firebase Analytics to track the interaction with any links that we generate for our applications. But if we only require simple tracking, then we can use the automatic built-in analytics from the Dynamic Links panel within the Firebase Console where we can also obtain attribution and referrer information for interacted links with no extra effort required from our side.

What makes it different from Google Analytics?

One of the first things that came to my mind when I read about Firebase Analytics was, “What about my Google Analytics setup?”. So if you already have Google Analytics in place, then why would you make the switch to Firebase Analytics? Well, here’s a couple of differences between the two:

Audiences

We can use Firebase Analytics to create Audiences — these are groups of users that we can then interact with using other Firebase service such as Firebase Notifications and / or Firebase Remote Config.

Integration with other Firebase Services

An awesome thing with Firebase Analytics is that we can integrate other Firebase services with analytics. For example, creating an Audience of users who have experienced a crash reported through Firebase Crash Reporting.

Lower Method Count

The Google Analytics dependency on Android has a total count of 18,607 methods and has a total of 4kb used for dependancies. On the other hand, Firebase Core (for Analytics) has a method count of 15,130 and only 1kb used for dependancies.

Automatic Tracking

When we add the firebase core dependency, it will automatically begin tracking a collection of user engagement events and device information for us — this is useful if you’re looking to only collect the minimal data for your app.

Unlimited Reporting

For up to 500 events, Firebase Analytics provides us with unlimited reporting straight out of the box for free!

No Singleton Initialisation

When setting up Google Analytics on Android we are required to initialize a Singleton instance. Firebase Analytics are simply available by fetching the instance directly from where we wish to track data. This isn’t much effort obviously but just makes the setup flow slightly easier.

Single Console

All of the data for every Firebase service is available for a single console. That makes it both easier and quicker for us to navigate from checking the analytic stats for our app to viewing the latest crash reports.

Community
  • 1
  • 1
Rohit Sharma
  • 1,271
  • 5
  • 19
  • 37
0

It looks like this is a react-native-firebase open bug for android

For fix the only thing that is required to be changed in module code:

private boolean isInvitation(PendingDynamicLinkData pendingDynamicLinkData) {
    return FirebaseAppInvite.getInvitation(pendingDynamicLinkData) != null;
}

to

private boolean isInvitation(PendingDynamicLinkData pendingDynamicLinkData) {
    FirebaseAppInvite invite = FirebaseAppInvite.getInvitation(pendingDynamicLinkData);
    if (invite != null && invite.getInvitationId() != null && !invite.getInvitationId().isEmpty()) {
        return true;
    }
    return false;
}

Bug reference : https://github.com/invertase/react-native-firebase/issues/1273

NullPointer
  • 7,094
  • 5
  • 27
  • 41
0

Please Check Your Manifest file open AndroidManifest.file => In your activity tag there is intent-filter tag put below line in that tag.

<data android:scheme="https" android:host="your.dynamic.link" />
<data android:scheme="http" android:host="your.dynamic.link" />

If already done then check this link for the full blog on the dynamic link with react native. Link: http://blog.logicwind.com/react-native-dynamic-links-using-firebase/

I hope this will help. sorry for the typos.

husen
  • 180
  • 1
  • 2
  • 11