Updated checksum to match binary artifact

[andibeqiri]

No description provided.

[JeremieDaigle2]

Anytime you guys are ready ! :D this is blocking
#276 (comment)
We cleared our caches, its still not working though

[galunecandrey]

Please consider this PR as soon as possible. We also have this problem on CI/CD. One of the packages we use has a dependency on AppsFlyerLib. Clearing caches doesn't help.

[JohnnyTseng]

@af-obodovskyi Would you please merge this PR? Thank you!

[srdanrasic]

@amit-kremer93 @af-obodovskyi could you look into this with urgency? This is breaking many organisation's CIs.

[JeremieDaigle2]

is there any good reason why this isnt merged in yet? this is blocking...

[hbanzon]

Thank you for prepping this PR! I could benefit from it as well 🙏

[richroguetech]

Please merge this. I need this!

[af-obodovskyi]

@richroguetech , @hbanzon , @srdanrasic , @JohnnyTseng

@scottlemke Please consider using one of the following repositories for the SPM. SPM support will be removed from the main repository because of the extremely long checkout time, which affects the SPM package integration time.

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

[ftp27]

@af-obodovskyi what release processes are you talking about? It's just links to binaries and zero source code :D With the same result you can publish separate version tags in separate branches

[af-obodovskyi]

@ftp27 not the release process, SPM package integration time. I will edit my comment

[richroguetech]

@af-obodovskyi can someone explain this? I used your repos and i got this:

. The /Frameworks/AppsFlyerLib.framework' specifies a MinimumOSVersion of '100.0' but contains a 32-bit architecture that is unsupported on iOS 12 and later.

Apple Developer Relations

[hbanzon]

@af-obodovskyi I get the following error using the Static library. Seems liek there's some changes that will be required on our end if we switch repos.

AppsFlyerLib is not a valid configured external dependency

[hbanzon]

Can we get more of a ramp up time to adapt to the new repos but in the meantime merge any of the PRs that fix this issue?

[scottlemke]

@af-obodovskyi I get the following error using the Static library. Seems liek there's some changes that will be required on our end if we switch repos.

AppsFlyerLib is not a valid configured external dependency

@hbanzon I assume you're using Tuist too? If so, you need to reference the static of dynamic library name to fix that issue. Something like:
.external(name: "AppsFlyerLib-Static") or .external(name: "AppsFlyerLib-Dynamic")

[hbanzon]

Thank you @scottlemke!