Skip to content
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

[doc] Initializing SDK vs initializing callbacks is confusing #341

Open
joshuadeguzman opened this issue Sep 10, 2024 · 1 comment
Open
Labels

Comments

@joshuadeguzman
Copy link

Describe the bug

In the Deep Linking documentation, it clearly outlined that Note: The code implementation for onInstallConversionData must be made prior to the initialization code of the SDK.. However, in the examples, like this, the initSdk is called prior to the callback invocation.

What's working for us so far is by following the example.

Problems

  • The docs create confusion for us, and potentially other integrators which is actually the pattern that must be followed for setting up the SDK

Proposal

  • It would be best to have the docs get updated, have stay consistent which is the correct way to initialize the SDK
  • Clean up the example doc, remove unused, commented code
Copy link

👋 Hi @joshuadeguzman and Thank you for reaching out to us.
In order for us to provide optimal support, please submit a ticket to our support team at [email protected].
When submitting the ticket, please specify:

  • ✅ your AppsFlyer sign-up (account) email
  • ✅ app ID
  • ✅ production steps
  • ✅ logs
  • ✅ code snippets
  • ✅ and any additional relevant information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants