facebook-ios-sdk
facebook-ios-sdk copied to clipboard
(Reopen) FBSDKLog: starting with Graph API v2.4, GET requests for /{appId}/model_asset should contain an explicit "fields" parameter
Checklist before submitting a bug report
- [X] I've updated to the latest released version of the SDK
- [X] I've searched for existing GitHub issues
- [X] I've looked for existing answers on Stack Overflow, the Facebook Developer Community Forum and the Facebook Developers Group
- [X] I've read the Code of Conduct
- [X] This issue is not security related and can safely be disclosed publicly on GitHub
Xcode version
15.3
Facebook iOS SDK version
17.0.1
Dependency Manager
CocoaPods
SDK Framework
Core
Goals
FBSDKLog: starting with Graph API v2.4, GET requests for /{appId}/model_asset should contain an explicit "fields" parameter FBSDKLog: starting with Graph API v2.4, GET requests for /{appid}/ios_skadnetwork_conversion_config should contain an explicit "fields" parameter I get these issues with latest sdk, The older issue is closed but there are some recent comments added after issue was closed that indicate that I'm not the only person experiencing this issue.
Expected results
Not to get this error
Actual results
There is no stack trace in the log, just this meesage
Steps to reproduce
Launch app as normal
Code samples & details
I'm not explicitly call this these calls, they are called from the Facebook Unity SDK and subsequently the ios version of Facebook sdk The older bug 1403 (2020) is the same but was closed, but there are new comments indicating it's occuring with latest
This is a reopen of https://github.com/facebook/facebook-ios-sdk/issues/1403. After that was closed, there were some comments reporting that the issue still persists, and it's also the case for me, using 17.3.0 with SPM.
same issue on 17.4
same issue on 17.0.1
Still getting on 17.4.0 (SPM). Using Xcode 16.2 Mac OS 15.2
This is happening while share feature. Also content is not shared on feed.
Same issue here on v17.4 and v18.0. We do not use the Graph API directly anywhere in our app — the call seems to be happening internally within the SDK itself.