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

XCFramework signing error #4146

Open
XericDesign opened this issue Aug 5, 2024 · 1 comment
Open

XCFramework signing error #4146

XericDesign opened this issue Aug 5, 2024 · 1 comment
Labels

Comments

@XericDesign
Copy link

XericDesign commented Aug 5, 2024

I have migrated from the framework to the xcframework in a macOS project. Everything was working before.

This is a 100% Cocoa project. No Swift.

After cleaning the project, during compile I get:

#import <RevenueCat/RevenueCat.h>. "'RevenueCat/RevenueCat.h' file not found"

Building a second time seems to get past this but then I get an OS-generated window saying "RevenueCat.framework" cannot be opened because the developer cannot be verified.

In my Framework search Paths, I have the parent folder where the RevenueCat.xcframework is stored in my project folder.

My project is set to automatic signing, the build phase has a Copy Files section where RevenueCat.xcframework is copied and signed on copy. In the General Build Tab, RevenueCat.xcframework is set to Embed & Sign.

The other curious thing is after building, there is a copy of the framework in my app bundle as expected but Xcode also places a copy of the framework in the same folder as my app. This is when I build for running in the debugger.

If I pull the appropriate .framework out of the .xcframework, and use it in my project, everything works as expected.

Xcode 15.4

How can I fix this?

@XericDesign XericDesign added the bug label Aug 5, 2024
@RCGitBot
Copy link
Contributor

RCGitBot commented Aug 5, 2024

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

aboedo added a commit that referenced this issue Aug 15, 2024
We don't currently export RevenueCatUI as an xcframework, which can be a
source of confusion and a dealbreaker for customers who need a pre-built
framework.
This adds RevenueCatUI's xcframework into the `export_xcframeworks`
lane, and includes the output in the `github_release` lane.


Should help address: 
- #4168
- #4146
- #4056
nyeu pushed a commit that referenced this issue Oct 2, 2024
We don't currently export RevenueCatUI as an xcframework, which can be a
source of confusion and a dealbreaker for customers who need a pre-built
framework.
This adds RevenueCatUI's xcframework into the `export_xcframeworks`
lane, and includes the output in the `github_release` lane.


Should help address: 
- #4168
- #4146
- #4056
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants