You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is not security related and can safely be disclosed publicly on GitHub
Xcode version
Xcode 15.0 Beta 6 (15A5219j)
Facebook iOS SDK version
16.1.3
Dependency Manager
CocoaPods
SDK Framework
Login
Goals
Warning-free compilation
Expected results
Compilation completes without warnings
Actual results
Compilation competes with following warnings:
ld: warning: duplicate LC_RPATH are deprecated ('@executable_path/Frameworks')
ld: warning: duplicate LC_RPATH are deprecated ('@loader_path/Frameworks')
Steps to reproduce
Integrate FBSDKLoginKit to iOS project via CocoaPods
Compile project with Xcode 15 Beta 6
After compilation completes get warnings in compile target linking step
Initially Xcode doesn't specify which binary generates this warning, to find out it I copy target linking 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.
/Applications/Xcode-15.0.0-Beta.6.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -Xlinker -t ....very long args list....
Output:
...
/Users/kattouf/Library/Developer/Xcode/DerivedData/MyApp-cwrffmwjdlzeiyarzpcebcovosub/Build/Products/Debug-iphonesimulator/XCFrameworkIntermediates/FBAEMKit/FBAEMKit.framework/FBAEMKit
ld: warning: duplicate LC_RPATH are deprecated ('@executable_path/Frameworks')
ld: warning: duplicate LC_RPATH are deprecated ('@loader_path/Frameworks')
...
/Users/kattouf/Library/Developer/Xcode/DerivedData/MyApp-cwrffmwjdlzeiyarzpcebcovosub/Build/Products/Debug-iphonesimulator/XCFrameworkIntermediates/FBSDKCoreKit/FBSDKCoreKit.framework/FBSDKCoreKit
ld: warning: duplicate LC_RPATH are deprecated ('@executable_path/Frameworks')
ld: warning: duplicate LC_RPATH are deprecated ('@loader_path/Frameworks')
...
/Users/kattouf/Library/Developer/Xcode/DerivedData/MyApp-cwrffmwjdlzeiyarzpcebcovosub/Build/Products/Debug-iphonesimulator/XCFrameworkIntermediates/FBSDKCoreKit_Basics/FBSDKCoreKit_Basics.framework/FBSDKCoreKit_Basics
ld: warning: duplicate LC_RPATH are deprecated ('@executable_path/Frameworks')
ld: warning: duplicate LC_RPATH are deprecated ('@loader_path/Frameworks')
...
/Users/kattouf/Library/Developer/Xcode/DerivedData/MyApp-cwrffmwjdlzeiyarzpcebcovosub/Build/Products/Debug-iphonesimulator/XCFrameworkIntermediates/FBSDKLoginKit/FBSDKLoginKit.framework/FBSDKLoginKit
ld: warning: duplicate LC_RPATH are deprecated ('@executable_path/Frameworks')
ld: warning: duplicate LC_RPATH are deprecated ('@loader_path/Frameworks')
...
Then I manually checked one of arm64 binary to confirm the warning by printing load commands:
Checklist before submitting a bug report
Xcode version
Xcode 15.0 Beta 6 (15A5219j)
Facebook iOS SDK version
16.1.3
Dependency Manager
CocoaPods
SDK Framework
Login
Goals
Warning-free compilation
Expected results
Compilation completes without warnings
Actual results
Compilation competes with following warnings:
Steps to reproduce
Initially Xcode doesn't specify which binary generates this warning, to find out it I copy target linking 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.
Output:
Then I manually checked one of arm64 binary to confirm the warning by printing load commands:
otool -arch arm64 -l Pods/FBSDKLoginKit/XCFrameworks/FBSDKLoginKit.xcframework/ios-arm64/FBSDKLoginKit.framework/FBSDKLoginKit | rg -A 2 -B 1 LC_RPATH
And got output, where we see that
@executable_path/Frameworks
and@loader_path/Frameworks
are defined twice:Code samples & details
No response
The text was updated successfully, but these errors were encountered: