manualStart
option still requires onDeepLink to be set before initSdk
#574
Labels
manualStart
option still requires onDeepLink to be set before initSdk
#574
Report
Plugin Version
6.12.2
On what Platform are you having the issue?
iOS (probably also Android)
What did you do?
Tried to subsequently register a deeplink handler between
initSdk
andstartSdk
withmanualStart
option set totrue
What did you expect to happen?
I would have expected the appyFlyer SDK to allow me adding the deeplink listener subsquently so that the deeplinkHandler gets fired only after the SDK got started through
appsFlyer.startSdk()
What happened instead?
Once the app is fully closed and we try to open a deeplink, we see the
Sending
onDeepLinkingwith no listeners registered
warning appearing.Please provide any other relevant information.
We are using
react-navigation
with linking for deeplinking. To be able to get access to the navigation/linking, the appsFlyer init has to be placed within the<NavigationContainer>
.The complexity exists because we want to send an
AppStart
event once the app has been launched and theApp.tsx
got executed. To be able to do that, theappsFlyer.initSdk()
has to be executed before the firstappsFlyer.logEvent()
gets fired.I would expect the onDeepLink to work the same way so that it's possible to run
initSdk
, set anonDeepLink
listener and then finallystartSDK
once everything is ready.Example pseudo-code:
The text was updated successfully, but these errors were encountered: