facebook-ios-sdk
facebook-ios-sdk copied to clipboard
I want to updating Facebook SDK to 17.0.0 bug it is fail ,please update to 17.0.0
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.2
Facebook iOS SDK version
17.0.0
Dependency Manager
CocoaPods
SDK Framework
Core
Goals
I want to updating Facebook SDK to 17.0.0 bug it is fail ,please update to 17.0.0
Expected results
I want to updating Facebook SDK to 17.0.0 bug it is fail ,please update to 17.0.0
Actual results
I want to updating Facebook SDK to 17.0.0 bug it is fail ,please update to 17.0.0
Steps to reproduce
I want to updating Facebook SDK to 17.0.0 bug it is fail ,please update to 17.0.0
Code samples & details
I want to updating Facebook SDK to 17.0.0 bug it is fail ,please update to 17.0.0
I'm currently using Facebook SDK version 16.3.1 in my Swift project,but ,it don't include Privacy Manifests,please update 17.0.0
Apps uploaded to App Store Connect must be built with Xcode 15 for iOS 17, iPadOS 17, tvOS 17, or watchOS 10, starting April 29, 2024. quote link
Without this change app developers using facebook iOS sdk will not be able to update their apps in the app store after April 29th, 2024. Please fix.
From what I gather looking at the repository, 17.0 is not pushed to Cocoapods specs repo and the podspec file doesn't even contain the privacy manifest in resources like it should.
Please look at all the other maintained projects on GitHub if you're not sure how to include it, but if this isn't fixed soon we'll be forced to remove the SDK from our project.
FBSDKTVOSKit also need, please
@MatyasKrizN I updated my Podfile, and could retrieve the 17.0 version, so it seems to be updated now.
doesn't even contain the privacy manifest in resources
It seems the pod contains the compiled version of the sdk as a xcframework, not directly the sources. I think it is the correct way to embed the privacy manifest, for compiled sdks, compared to sources pod that indeed needs to contain privacy manifest in resources of the pod, in order to add it at the compilation of the pod.