Skip to content

Signing issues when part of the Unity SDK #5740

@bitsandfoxes

Description

@bitsandfoxes

Description

In the context of having the Cocoa SDK as part of the Unity SDK: Xcode builds fails with The signature of "Sentry.xcframework" cannot be verified.

Investigation

The issue can be narrowed down to

  • The Unity SDK copies the xcframework "by hand"
  • Symlinks get lost or break

I could attempt to fix this partly inside the Unity SDK. But it will still break for users that i.e. export an iOS Xcode project on Windows and only build that project on macOS - which can be considered a typical workflow.

Taking a look at the xcframework structure we see the following differences in

  • ios-arm64_arm64e_x86_64-maccatalyst
  • macos-arm64_arm64e_x86_64

where these have symlinks from their root directories inside the .framework into Versions/. Note, there is only one version.

Image

Question

Is this structure for these targets a requirement? Can we have it without symlinks - like all the others - instead?

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions