Deffered deep linking for new users not fired at app open
Hi,
I'm using SDK version 4.35.2 and I'm having a similar problem as Domagojb here with deffered deep linking for new users. Using deffered deep linking while the app is installed is working correctly, the issue is only for new users.
I followed this 4 steps process: https://help.adjust.com/en/article/test-adjust-deep-links#as-a-new-user But I get a problem at step 4: I'm not direclty deep linked to the specific location written in our custom URI scheme, I'm only deep linked when an answer to the ATT alert is provided (when user tap on "Allow" or "Ask App Not to Track" in the ATT alert)
Is it an expected behavior? I would expect the deep link is triggered as soon as the app is opened, without waiting the answer to the ATT alert. We need to show to the user a customised onboarding depending of the deep link, so we need it to be executed asap. Actually we already do this using a Firebase Dynamic Link, but we would like to replace this with an Adjust deep link.
For more detail, few details how we perform this 5 steps process:
- I remove the app from the device
- I made sure the device is forgotten with Testing Console for the app
- I execute the following deeplink with a tap on a link on our custom web site:
https://app.adjust.com/{trackerId}?deep_link={bundleId}%3A%2F%2FtermsI'm redirected to the App Store - I download the app from the App Store and I open it
- When the app opens, we show the ATT alert. When I tap "Allow" or "Ask App Not to Track", the
deep_linkdefined at step 3 is executed
I would expect the deep link is triggered as soon as the app is opened, without waiting the answer to the ATT alert.
Thanks for your help.
Hi @squall2022,
And sorry for the delay in response. Thank you also for a very detailed explanation of the situation. Before checking for some other things, can I ask you to enable sending of things from Adjust SDK while app is in background (also not in focus) by doing this on your ADJConfig instance:
[adjustConfig setSendInBackground:YES];
retry the test and let me know if you're still seeing the same behavior or not?
Hi @uerceg,
Thanks for you answer. I just tested and it doesn't change the behavior I described.