-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Distributed FacebookSDK includes references to absolute paths on Facebook developer's machine #1203
Comments
This is interesting. Couple questions: |
@joesus Here is the relevant section of my
Here is the relevant section of my
Finally, the warnings were produced in the build logs during the "Generate dSYM" step. I was building on the desktop in the Xcode 11.3.1 IDE using the Build option (command-B). Configuration for my active scheme's Build action is Debug, target device was a physical 64-bit iOS device. |
I'm encountering the exact same issue. Were you able to resolve? |
This seems to be only reproducible when:
|
It turns out the all the FacebookSDKs installed by cocoapods were 5.15. Switched to using Xcode’s built in Swift Package Manager which installed version 6.0 which solved the issue. |
Unfortunately, this is still reproducible in v6.0 when installed using Cocoapods |
Same problem as well. How can I resolve without changing the 'DWARF with dySYM File' to 'DWARF? |
I solved by using Swift Package Manager (SPM) to install the FacebookSDK v6.0. However as @kjen93 mentioned, what may actually have fixed the issue is the fact that cocoapods may have been installing Facebooks MarketingKit (which I wasn’t actually using) whereas SPM didn’t - and this the issue may exist in MarketingKit rather than being an issue with v5.15 itself. |
I didn't need all functionality, just CoreKit, so I change:
for
And every warning disappeared. |
@KylinChang After you release the last facebookSDK for CocoaPods #1298 , now the warning show up your name path. Could you help to take a look? |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. Thank you for your contributions. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
I found it here Pods/FBSDKMarketingKit/FBSDKMarketingKit.framework/FBSDKMarketingKit |
I'm still seeing this with manual non-cocoapods integration of the prebuilt frameworks:
@joesus You can get rid of this by setting |
I have same issue using SPM (I import only FacebookCore target), sdk version 14.1.0 |
Checklist
Environment
Describe your dev environment here, giving as many details as possible. If you have them, make sure to include:
11.3.1
5.1
(if issue is Swift related)1.8.4
5.15.0
Goals
What do you want to achieve?
Integrate the FBSDK without build errors or warnings.
Expected Results
What do you expect to happen?
Build after integrating the FBSDK without build errors or warnings.
Actual Results
What actually happened? Can you provide a stack trace?
Found the following warnings when building to a device:
Steps to Reproduce
What are the steps necessary to reproduce this issue?
Integrate the FBSDK
Build to a device
Code Samples & Details
None should be required.
The text was updated successfully, but these errors were encountered: