Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing signature for GoogleToolboxForMac.framework #41

Open
marianhunchak opened this issue May 16, 2024 · 1 comment
Open

Missing signature for GoogleToolboxForMac.framework #41

marianhunchak opened this issue May 16, 2024 · 1 comment

Comments

@marianhunchak
Copy link

ITMS-91065: Missing signature - Your app includes “Frameworks/GoogleToolboxForMac.framework/GoogleToolboxForMac”, which includes GoogleToolboxForMac, an SDK that was identified in the documentation as a privacy-impacting third-party SDK. If a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a signature file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a signature. For details about verifying the code signature for a third-party SDK, visit: https://developer.apple.com/documentation/xcode/verifying-the-origin-of-your-xcframeworks.

@sallyluenoa
Copy link

Hi @d-date,

I also have the same issues, and unfortunately I failed to upload to the TestFlight…

According to the swift package file Package.swift, the library module GoogleToolboxForMac is downloaded from the release Assets, that version is the latest version v6.0.0.

    .binaryTarget(
      name: "GoogleToolboxForMac",
      url:
        "https://github.com/d-date/google-mlkit-swiftpm/releases/download/6.0.0/GoogleToolboxForMac.xcframework.zip",

I downloaded this framework and I found there are no privacy manifest files in the framework!
Further more, the Bundle version string (short) is “2.3.2” when checking Info.plist!

No_PrivacyInfo_GoogleToolboxForMac

Thus I think the problem is the library version is too old.
My suggestion is please update to the latest version v4.2.1 that is contained the privacy manifest, then I believe it would be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants