-
Notifications
You must be signed in to change notification settings - Fork 739
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
apollo-ios-xcframework fails to build #3439
apollo-ios-xcframework fails to build #3439
Comments
@CraigSiemens thanks for the detailed report, I'll have a look at this so we can get it fixed. |
Looked into this briefly so far, it looks like the schemes available in the project are shared, and there are targets for the package products but not actually schemes, so I'm not positive the schemes are the root issue here. I did notice when running Will look into this some more soon to see if I can narrow it down further. |
Since the schemes are missing from |
Hmmm I can check that, although the |
@CraigSiemens So I was playing around with this, turned off the option in Tuist that was disable the auto-generation of schemes and regenerated the project/workspace and the make command started working as expected again. I have a pull request up with for the potential fix, would you be able to point to that branch and see if it solves your Carthage issue? |
Yeah, I'll try it out. |
Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo iOS usage and allow us to serve you better. |
Summary
It appears that the apollo-ios-xcframework repo no longer contains any shared or generated schemes causing carthage to be unable to build.
Related to #3308
Version
Tried with the latest version 1.15.1. Possibly occurs on older versions, we're very slow to update 🐢.
Steps to reproduce the behavior
Logs
Anything else?
Also, I tried manually calling the makefile to build the frameworks but that also results in an error since it appears the
iphoneos.xcarchive
doesn't contain a framework.I think it's also caused by there being no shared schemes. If I manually create a new scheme in the project, it shows the project targets and the package targets.
I'd guess the
xcodebuild
command picks the package target when specifying-scheme Apollo
and building for iOS. After manually creating the schemes, it produces the xcframeworks.The text was updated successfully, but these errors were encountered: