Hello 👋, thanks for your request, and yes we are planning this, but that is not on top of our backlog for now.
We are planning to switch CocoaPods to build from source (vs binaries) in the near future as you can see with 4.0.0-alpha1
Swift Package Manager might come along.
Also, we are open to contributions... 😉

Hello,
Do you have any news about the SPM support ? You are the only libraries which is not supporting SPM in our project at the moment.
Best regards,
Denis

Hi,

We are minimising usage of Cocoapods and switching to SPM.
Any news about SPM or at least Carthage support?

Thank you in advance,
Vlad.

Maybe this can unblock some of you, I was able to add Criteo as a dependency of my package by using a binaryTarget:

 targets: [
        .target(
            name: "MyTarget",
            dependencies: [
                "CriteoPublisherSdk",
            ],
            path: "ios/Sources",
            exclude: [],
            resources: [ ]
        ),
        .binaryTarget(
            name: "CriteoPublisherSdk",
            url: "https://github.com/criteo/ios-publisher-sdk/releases/download/4.7.0/CriteoPublisherSdk.Release.zip",
            checksum: "55031718f5a617374aba6c91fad1e0956016a8ab68dc9f28252a643a6f5a4936"
        )
]

bump @vguerci

Soon 4 years and still no official support

https://github.com/criteo/ios-publisher-sdk/releases/download/4.7.0/CriteoPublisherSdk.Release.zip

Unfortunately, not all header files are available when different packages try to integrate it with this method.

Additionally, CocoaPods is now in maintenance mode - so official support from the author is important IMO.

I will try to map a Package.swift file after the holidays but since I have no clue how the dependencies are intertwined it may take longer and probably support from officials as well.