-
Notifications
You must be signed in to change notification settings - Fork 92
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
Xcode 15 linker warnings #251
Labels
Comments
I have noticed the same warning as well on beta 8, but only after updating to version |
Xcode 15 is coming soon, do you have any updates? |
bump |
@kattouf we will fix this issue in the upcoming release of the AppsFlyerSDK |
bump |
I'm also interested in a fix here |
I'm waiting for a solution too. |
bump |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Report
SDK Version
6.12.1
integrated via CocoaPods (AppsFlyerFramework/Dynamic)
What did you do?
Compile iOS project with new
Xcode 15.0 Beta 6 (15A5219j)
What did you expect to happen?
Compilation completes without warnings
What happened instead?
Compilation competes with following warnings:
Please provide any other relevant information.
I manually checked arm64 binary to confirm the warning by printing load commands:
otool -arch arm64 -l Pods/AppsFlyerFramework/binaries/xcframework/dynamic/AppsFlyerLib.xcframework/ios-arm64_armv7/AppsFlyerLib.framework/AppsFlyerLib | rg -A 2 -B 1 LC_RPATH
And got output, where we see that
@executable_path/Frameworks
and@loader_path/Frameworks
are defined twice:Initially Xcode doesn't specify which binary generates this warning, to find out it I copy compile command from Xcode's build log and run it directly in the terminal, adding argument for additional linker logging:
-t Logs each file (object, archive, or dylib) the linker loads. Useful for debugging problems with search paths where the wrong library is loaded.
The text was updated successfully, but these errors were encountered: