Referring Identity is null when parsing branch link url
See original GitHub issueAfter creating sharing url with setIdentity() and link() method, the generated url is not containing the referring_identity
or identity
. This values are coming as null
Steps to reproduce (on https://cdn.branch.io/example.html):
- init()
- setIdentity()
- link()
Click on the generated link.
In Session Info the response doesn’t contain the mentioned info (referring_identity
or identity
).
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:12 (3 by maintainers)
Top Results From Across the Web
Deep Linking API - Branch Help
Branch's Deep Linking API is a powerful tool for all things Branch Links. You can programmatically generate links at scale to support all...
Read more >Getting referringParams of onInitFinished null unless kill the ...
I am using branch in android app for deep linking, referringParams of onInitFinished are coming as null . If I kill the app...
Read more >Deep linking in Android — Part 2 - Medium
Follow the below mentioned steps to create the URL on web: Sign up/Sign in your Branch account and open the main dashboard; Click...
Read more >NavigationContainer | React Navigation
The NavigationContainer is responsible for managing your app state and linking your top-level navigator to the app environment.
Read more >branch-sdk - npm
Branch Metrics Deep Linking/Smart Banner Web SDK. ... Returns the initial referring data for this identity, if exists, as a parsed object.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Facing the same issue, did you resolve?
I’m going to close this issue out and we’ll determine what to do about the referring_identity internally. Thank you for bringing this to our attention once again!