-
Notifications
You must be signed in to change notification settings - Fork 202
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
onInstallConversionData dosen't return onAppOpenAttribution when mounting #53
Comments
hey @katjastrof , are we talking about Android or iOS (+ OS version)? also please provide relevant code snippets of integration with AppsFlyer SDK. |
I'm using Android. I'm using the react-native-appsflyer 1.2.13 and the Android OS I've tested on is 7 and 8.
It's the |
I'm also experiencing this issue. When clicking a deeplink, Here's my implementation along with some log outputs for the various cases: https://gist.github.com/bfinamore/a5e5c2f94861b7d49ee5f05f91223ae0 SDKs: RN version: 0.55.4 Tested on: |
Will be fixed in next week v1.4.0 |
@af-fess is there any update on v1.4.0? |
@santiph we have a fix on the native side of SDK. So we are going to release Android We already tested it with the beta version and everything works as expected. Thank you, |
@katjastrof we tested a staging version, so far you can try this branch:
For testing, we use dummy App.js:
|
This is happening on android sdk as well, and I believe they don't have fix for it yet. |
I get a success callback from onInstallConversionData every time opening the app. I can get both callbacks of type onInstallConversionDataLoaded and onAppOpenAttribution.
But I don't get the onAppOpenAttribution when mounting the app for the first time even if I pressed a referal-link.
If I have the app running in background and pressing the referallink I get an onAppOpenAttribution callback. If I open the app with the link and then open it from the background I get the onAppOpenAttribution when opening from background.
Do you now if this is how it suppose to be?
The text was updated successfully, but these errors were encountered: