I’m testing the deferred deep linking function of AppsFlyer, however I am unable to get a brand new deep hyperlink to attribute appropriately after a re-installation. The SDK appears to be caching the information from the preliminary set up.
Steps to Reproduce
-
I’ve not but put in the app on my check machine.
-
I click on on an AppsFlyer OneLink (Hyperlink A).
-
For the reason that app just isn’t on the Play Retailer, I manually set up a debug APK of my utility from Android Studio.
-
Upon opening the app, the
onDeepLink
UDL (Unified Deep Linking) technique known as, and I efficiently obtain the deferred deep hyperlink knowledge for Hyperlink A. -
I instantly uninstall the app from the machine.
-
I repeat the method, however this time I click on a completely different OneLink (Hyperlink B).
-
I reinstall the app from Android Studio.
My Query
Why is AppsFlyer not re-attributing the second set up to the brand new deep hyperlink (Hyperlink B)? What’s the right process to totally reset the machine’s state and simulate a brand new consumer for a deferred deep hyperlink check on the identical machine?
Anticipated Habits
-
I anticipated the
onDeepLink
technique to supply me with the deferred deep hyperlink knowledge for Hyperlink B, as I clicked a brand new hyperlink with the app uninstalled.Precise Habits
On the second set up, the
onDeepLink
technique known as, however theDeepLinkResult
object comprises the information from the unique Hyperlink A. Thestanding
can also be incorrectly reported as an natural launch.It looks as if AppsFlyer just isn’t clearing the attribution knowledge after the uninstall, resulting in it incorrectly returning the outdated knowledge and misreporting the attribution kind.