-
Notifications
You must be signed in to change notification settings - Fork 96
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Cannot archive build on Xcode 13 beta 3 #31
Comments
Hi @d-date! I'm able to successfully build a project that depends on CombineSchedulers in beta 3. The error message you posted makes it sound like you have a custom toolchain selected in Xcode. Can you check the "Xcode > Toolchains" menu and verify that "Xcode 13.0" is selected? The only other thing I can think of is maybe you have some stale build products getting in the way. "Product > Clean Build Folder" could help, or you could try fully deleting the Derived Data folder. |
@stephencelis As you say, I checked that Xcode 13 was selected as the toolchain. I also tried a clean build, but didn't change. |
I am also seeing this error. Although to start I am suspecting beta 3 or maybe something about my workspace configuration more than combine-schedulers per se. I don't think I have any alternative toolchains installed. (The toolchain items don't even appear in the Xcode menu or Preferences > Components.) Deleted derived data. M1 Mac, if it matters. |
Seems to be the same issue: https://developer.apple.com/forums/thread/682285?answerId=682006022#682006022 |
😢 oof, good to know. I'm going to covert this to a discussion since it's not really a CombineSchedulers issue and so that we can continue sharing information about it. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Describe the bug
When running archive build on Xcode 13 beta 3, the build fail since it depends on Combine.framework built by different compiler version.
Screenshots
Environment
The text was updated successfully, but these errors were encountered: