Wrong version in SPM Xcode 15.3, latest release 17.0.0 but SPM package declares 14.1.0

[Volodymyr-13]

Checklist before submitting a bug report

• I've updated to the latest released version of the SDK
• I've searched for existing GitHub issues
• I've looked for existing answers on Stack Overflow, the Facebook Developer Community Forum and the Facebook Developers Group
• I've read the Code of Conduct
• This issue is not security related and can safely be disclosed publicly on GitHub

Xcode version

15.3

Facebook iOS SDK version

https://github.com/facebook/facebook-ios-sdk

Dependency Manager

SPM

SDK Framework

Other / I don't know

Goals

Integrate via SPM a https://github.com/facebook/facebook-ios-sdk latest version

Expected results

Uses latest version from Releases

Actual results

It uses old version by default, not the latest from Releases

Steps to reproduce

Just add this repo via SPM

Code samples & details

No response

[ayushmahajan12]

@Volodymyr-13 , you can change the dependency rule and select the "Exact version" from the dropdown and enter the version 16.3.1, then try

[zhangwei5436]

updating Facebook SDK to 17.0.0 bug it is fail ，please update to 17.0.0

[zhangwei5436]

I want to updating Facebook SDK to 17.0.0 bug it is fail ，please update to 17.0.0

[zhangwei5436]

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

[Volodymyr-13]

Same here for 17.0.0

@ayushmahajan12 this should be updated in package here.. they just don't do this.. only they from all any other SDK's.. well facebook is facebook..

[RGG-jayoung]

This issue is caused by Facebook tagging the releases inconsistently. There are multiple entries for 14.1.0. All other releases are prefixed with a v. Swift package manager is prioritizing the numeric 14.1.0 naming scheme over the alphanumeric v14.1.0.

Here it is in context:

If Facebook were to remove the v prefix and use numeric version tags and/or keep everything consistent, then Xcode and SPM would pull in the correct version.

Using multiple schemes like this has caused issues like this in the past with other packages.

Facebook can you help?

[RGG-jayoung]

As an experiment, you can create a new blank Swift Package and manually link the dependencies:

// Package.swift
// swift-tools-version: 5.10
// The swift-tools-version declares the minimum version of Swift required to build this package.

import PackageDescription

let package = Package(
    name: "FacebookSPMTest",
    products: [
        // Products define the executables and libraries a package produces, making them visible to other packages.
        .library(
            name: "FacebookSPMTest",
            targets: ["FacebookSPMTest"]),
    ],
    dependencies: [
        .package(url: "https://github.com/facebook/facebook-ios-sdk", exact: .init(stringLiteral: "v16.3.1"))
    ],
    targets: [
        // Targets are the basic building blocks of a package, defining a module or a test suite.
        // Targets can depend on other targets in this package and products from dependencies.
        .target(
            name: "FacebookSPMTest",
            dependencies: [
                .product(name: "FacebookCore", package: "facebook-ios-sdk"),
                .product(name: "FacebookLogin", package: "facebook-ios-sdk")
            ]),
        .testTarget(
            name: "FacebookSPMTestTests",
            dependencies: ["FacebookSPMTest"]),
    ]
)

Specifying a direct commit hash for the release works and the products like FacebookCore and FacebookLogin are available.

let package = Package(
    name: "FacebookSPMTest",
    products: [
        // Products define the executables and libraries a package produces, making them visible to other packages.
        .library(
            name: "FacebookSPMTest",
            targets: ["FacebookSPMTest"]),
    ],
    dependencies: [
        .package(url: "https://github.com/facebook/facebook-ios-sdk", revision: "3fe31c1")
    ],
    targets: [
        // Targets are the basic building blocks of a package, defining a module or a test suite.
        // Targets can depend on other targets in this package and products from dependencies.
        .target(
            name: "FacebookSPMTest",
            dependencies: [
                .product(name: "FacebookCore", package: "facebook-ios-sdk"),
                .product(name: "FacebookLogin", package: "facebook-ios-sdk")
            ]),
        .testTarget(
            name: "FacebookSPMTestTests",
            dependencies: ["FacebookSPMTest"]),
    ]
)

Curiously, if you specify the exact version number without the v prefix directly in a Package manifest or in Xcode, things work.

dependencies: [
        .package(url: "https://github.com/facebook/facebook-ios-sdk", exact: .init(stringLiteral: "16.3.1"))
        // Doesn't Work
        // .package(url: "https://github.com/facebook/facebook-ios-sdk", exact: .init(stringLiteral: "v16.3.1"))
    ],

[ayushmahajan12]

zhangwei5436

Can I know, After updating SDK version i.e. 16.3.1 are you able to see the exact version on facebook developer account.

I updated the SDK version to 16.3.1 but I'm not able to see the that version on Meta developer account, it is displaying the 0.3.1 instead oi 16.3.1

[gun-bro98]

I also had this problem and tried to install with SPM, but there was no suitable version.
I figured it out after several attempts.

Please change the Facebook version in Package Dependencies of the project.

[gerchicov-vg]

@Volodymyr-13 why did you close this issue? It is still not resolved