visionOS in Release xcFramework

[fishandphil]

Good evening,
We've started our work to support visionOS natively and this includes supporting RevenueCat for visionOS.

We need xcFramework and usually find them in your release section: https://github.com/RevenueCat/purchases-
ios/releases/tag/4.25.4

While we can see that you have been working on it from some commit, while we download the xcFramework, we don't see its segment.

Can you let us know "why" and how we can fix it? Our product is using multiple framework and from our understanding, it is not great to use SPM creates a static library while we're looking for dynamic..

Thank you very much

[RCGitBot]

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

[NachoSoto]

Thanks for the report.

We build the XCFramework attached to each release using Carthage + the latest stable version of Xcode.
In order to include visionOS we'd need 2 things:

• Use Xcode 15 beta, which would probably make the framework unusable for apps to be deployed to the App Store
• Use [WIP] Add support for xrOS Carthage/Carthage#3343, which isn't available in a stable release of Carthage

The first part won't be an issue after Xcode 15 RC. But for Carthage, we'll need that PR or Carthage/Carthage#3345 to be released.

[NachoSoto]

I totally understand your pain wanting to use a dynamic library though. I wish SPM allowed configuring how to link dependencies.
This is a possible workaround for you: https://stackoverflow.com/a/70812112

[fishandphil]

Thank you for your speedy response and information.

Couldn't you consider making available a special xcFramework in the next Release that is labeled "Xcode beta 15", so it can be embedded in apps that wishes to use visionOS?
Temporarily until a RC comes out.. but since they will not release Vision Pro devices until next year, that might take a while..

Cheers

[NachoSoto]

An update here: we're going to look into moving away from Carthage (since it's pretty much abandoned) and using raw xcodebuild commands to generate our XCFrameworks. This way we'll be able to add a visionOS "slice".

I don't have an ETA for that but we'll keep you posted.

[NachoSoto]

Update: turns out our automation already builds the xcframeworks using xcodebuild directly. So we'll ship a release with it as soon as Xcode 15 RC is out :)

[fishandphil]

I totally understand your pain wanting to use a dynamic library though. I wish SPM allowed configuring how to link dependencies. This is a possible workaround for you: https://stackoverflow.com/a/70812112

@NachoSoto I went back to look at the link you posted here. Apparently, it is possible for SPM to create a dynamic library by simply adding the "type: .dynamic," to the ".library" array of the product within the package.swift file.

I am simply wondering why you don't do it yourself for the whole repository? there must be a reason?

Thank you 🙏🏻

[NachoSoto]

@NachoSoto I went back to look at the link you posted here. Apparently, it is possible for SPM to create a dynamic library by simply adding the "type: .dynamic," to the ".library" array of the product within the package.swift file.

Because that would remove the "automatic" behavior and force everyone to link it dynamically. But not including it, it allows Xcode to link dynamically or statically as needed.

[NachoSoto]

This will be fixed with #3583, shipped on the next major release.