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
In want to integrate FBAudienceNetwork via SPM because we are moving away from CocoaPods. You already provide a "manual download" option but the zip file contains two xcframework subfolders (one static and one dynamic). This folder structure makes it impossible to use the xcframework as a remote (URL-based) binary target in SPM.
Expected results
A) Ideally, you as the framework vendor would provide the SPM support directly. E.g. like Google does it for their ads sdk where they have a repository with SPM support which uses the pre-build a binary. See https://github.com/googleads/swift-package-manager-google-mobile-ads
B) Another option would be, that you provide two separate binary zip files as the "manual download" option (one for the static xcframework and one for the dynamic xcframework). The xcframework should be at the top-level of the zip. This way, we as consumers can access it as a binary target in our package file.
Code samples & details
No response
The text was updated successfully, but these errors were encountered:
Checklist before submitting a feature request
Goals
In want to integrate FBAudienceNetwork via SPM because we are moving away from CocoaPods. You already provide a "manual download" option but the zip file contains two xcframework subfolders (one static and one dynamic). This folder structure makes it impossible to use the xcframework as a remote (URL-based) binary target in SPM.
Expected results
A) Ideally, you as the framework vendor would provide the SPM support directly. E.g. like Google does it for their ads sdk where they have a repository with SPM support which uses the pre-build a binary. See https://github.com/googleads/swift-package-manager-google-mobile-ads
B) Another option would be, that you provide two separate binary zip files as the "manual download" option (one for the static xcframework and one for the dynamic xcframework). The xcframework should be at the top-level of the zip. This way, we as consumers can access it as a binary target in our package file.
Code samples & details
No response
The text was updated successfully, but these errors were encountered: