Скачать или смотреть Resolving Duplicate Static Library Links in Unity Frameworks

Encountering issues with the `AppsFlyerFramework` linking twice in Unity? This guide offers clear solutions to prevent duplicate static library linking in Xcode and Unity Framework integration.
---
This video is based on the question https://stackoverflow.com/q/67621125/ asked by the user 'yaoxp' ( https://stackoverflow.com/u/9928574/ ) and on the answer https://stackoverflow.com/a/70345604/ provided by the user 'Gavin' ( https://stackoverflow.com/u/3973959/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Linked the third-party static library twice when use UnityFramework

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Resolving Duplicate Static Library Links in Unity Frameworks: A Comprehensive Guide

When developing applications using Unity, particularly mobile games for iOS, developers often face challenges with third-party libraries. A common issue is the inclusion of the same static library in two separate links, leading to confusing errors and potential runtime issues.

The Problem: Duplicate Static Library Links

In this specific scenario, developers using the AppFlyer static library with a Unity project are running into a linking issue. The error messages indicate that the AppsFlyerProxyManager is implemented in both the application and the Unity framework, causing the system to throw warnings and behave unpredictably.

Details of the Issue

Unity Version: 2019.4

CocoaPods Version: 1.10.1

Xcode Version: 12.5

Podfile Content: The library is included in the UnityFramework, but also attempted to be linked in the Unity-iPhone target.

Error Messages: The common log entries repeatedly indicate that certain classes (AppsFlyerProxyManager and AppsFlyerCrossPromotionHelper) are implemented in both targets.

The Solution: Prevent Duplicate Linking

To solve the issue, it's essential to ensure that the static library isn't linked by both the UnityFramework and the Unity-iPhone targets. Let's break down the steps to avoid this problem:

1. Understanding UnityFramework vs. Unity-iPhone

UnityFramework: This is a dynamic library that can link to third-party libraries. If these libraries are declared in its source code, it will automatically link them during the build.

Unity-iPhone: This should not link the same libraries that UnityFramework has already linked.

2. Modifying the Podfile

Your initial attempt involved setting up the Podfile correctly, but here are improved steps to prevent Unity-iPhone from linking the same third-party static library:

[[See Video to Reveal this Text or Code Snippet]]

3. Key Takeaways

Ensure Only One Link: Make sure that Unity-iPhone does not attempt to link the AppsFlyerFramework since it's already linked in UnityFramework.

Override Static Framework: Utilize the pre_install hook in your Podfile to explicitly state which frameworks to treat as static, thereby ensuring they won’t be linked again in the Unity-iPhone target.

4. Check Your Build Settings

After making the changes, clear your build folder and rebuild the project.

Ensure your Xcode settings don’t enforce duplications or conflicting builds.

Conclusion

Resolving static library linking issues can be tricky, especially in a dynamic environment like Unity combined with iOS development. By carefully managing your Podfile and understanding how UnityFramework and Unity-iPhone interact, you can prevent linking the same libraries multiple times.

If issues persist despite following these guidelines, consider consulting with other developers or forums for additional insights.

Feel free to share your experiences or any alternative solutions you've found effective!