-
Notifications
You must be signed in to change notification settings - Fork 307
V4103 #255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
fa9e41c to
2f869e3
Compare
|
Sorry but if "No longer necessary to have attribution delegate to open deferred deeplinks", where should I apply the logic to handle them? |
|
Deferred deep link nowdays arrive as a response to attribution request that our SDK sends to backend usually couple of seconds after install has been tracked. Before the change, SDK wasn't interested in asking for attribution since In this change, we have just made modification that as soon as install is tracked, regardless of whether user has implemented attribution callback or not, SDK will ask the backend for attribution for the user. In case deferred deep link was present in the whole flow, SDK will get it in the answer from backend and open it for you. So in theory, if you're expecting deferred deep link to be opened in your app, if we assume that you have correctly set up everything in your app for deep linking handling, no additional setup is needed in Adjust SDK to get it. Once it arrives to our SDK from our backend, you can get it inside of |
|
@uerceg The problem I am trying to test them, so I download the app using that link and then try to run the development version but |
Version 4.10.3
Added
Fixed