5

I'm implementing a Firebase dynamic link mechanism in Android. We wanted to use Android SDK but to match users only when there is a one-to-one identification between users who clicks the link and user, which opened the app. In iOS there is MatchType.Unique that serves this purpose:

The match between the Dynamic Link and this device is exact, hence you may reveal personal information related to the Dynamic Link. https://firebase.google.com/docs/reference/swift/firebasedynamiclinks/api/reference/Enums/DLMatchType#unique

Unfortunately, I can't find anything close in Android SDK. I will appreciate any help here to find how to distinguish deep links of the unique match type in Android

Thanks

Yonatan Levin
  • 342
  • 5
  • 17
  • I would like to help but am having a hard time understanding what you are looking for. Might you be able to rephrase the question? Use steps such as 1. Dynamic link is sent 2. Some user tries to open link in app 3. If link was intended for said user, then show personal data. 4. If the wrong user clicked to open the link do not show personal data. AND if I am correct so far, what does it mean to be the wrong user? Is the link always intended for a single user? Or can multiple user accounts be deemed right/correct users? – Isai Damier Nov 25 '19 at 19:10
  • MatchType is only used to check either link opens first time or not, if it is unique (or default) then it must be first time, else it will return as week. Can you please explain more what exactly you want to achieve? – Lalit Jadav Nov 27 '19 at 05:29
  • @Yonatan, Did you found any alternative for Android ? – Anukool srivastav May 05 '21 at 10:16

1 Answers1

0

It seems from this part of documentation that the matchType parameter exists only in Swift.

Personally, what I did is creating an array saved in the SharedPreferences, of all the DynamicLink already handled. Then, I just need to check for all the DynamicLinks entering if they are part of this array, and ignoring them in such a case.

Seems that even after an hour, the last DynamicLink handled still remains kind of "active".