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

Segment AppsFlyer iOS Uses Dynamic AppsFlyer Framework #142

Open
waitbutY opened this issue Jul 3, 2024 · 0 comments
Open

Segment AppsFlyer iOS Uses Dynamic AppsFlyer Framework #142

waitbutY opened this issue Jul 3, 2024 · 0 comments

Comments

@waitbutY
Copy link

waitbutY commented Jul 3, 2024

The main AppsFlyer SDK has 3 options for client consumption:

 # For statically linked library
 https://github.com/AppsFlyerSDK/AppsFlyerFramework-Static

 # For dynamically linked library
 https://github.com/AppsFlyerSDK/AppsFlyerFramework-Dynamic

 # For Strict (No IDFA colection) library
 https://github.com/AppsFlyerSDK/AppsFlyerFramework-Strict

However, this Segment wrapper is locked using the Dynamic framework.
Is there a way to allow clients to specify if they want static (for faster package resolution) or strict (for compliance)?

I do see this issue from a year ago asking for the Dynamic framework to be used, but there is little detail in it about the decision:
#126

Related issue in main AppsFlyer SDK: AppsFlyerSDK/AppsFlyerFramework#294

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

No branches or pull requests

1 participant