The iOS leg needs a newer Xcode than macos-14 has - #21
Merged
Conversation
requires Xcode 26.6. The current version of Xcode is 15.4. .NET for iOS refuses to build against an Xcode older than the one its SDK was built for, and 26.5.10315 wants 26.6 while macos-14 ships 15.4. Nothing to do with the package; the leg never got as far as linking. macos-latest rather than a pin, which is the opposite of what every other leg does and is deliberate. The workload moves fast, a pin would need bumping each time it advances, and falling behind stops this leg rather than degrading it. The five desktop legs stay pinned because their runners have no such coupling. The Xcode version is now printed before the build. The error names the version wanted and the one found and says nothing about which image that was, which is the part that took a run to work out.
Contributor
API gate: additiveEvery symbol that existed still exists, unchanged. Nothing that compiled before stops compiling.
Enum and constant values are part of the measured surface: a renumbering keeps compiling and sends the wrong number to the driver, so it counts as a removal. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
.NET for iOS refuses to build against an Xcode older than the one its SDK was built for.
26.5.10315wants Xcode 26.6;macos-14ships 15.4. Nothing to do with the package — the leg never got as far as linking anything.macos-latestrather than a pin, which is the opposite of what every other leg does and is deliberate: the workload moves fast, a pin would need bumping every time it advances, and falling behind stops this leg rather than degrading it. The five desktop legs stay pinned because their runners have no such coupling.The Xcode version is now printed before the build. The error names the version wanted and the one found and says nothing about which image that was, which is the part that cost a run to work out.
Found by the first full CD run with all eight legs. That run also exposed something unrelated and worth knowing: a CD started with
publish-onlypacked six runtimes instead of nine, missingbrowser-wasm,ios-arm64andiossimulator-arm64— exactly the three that are gitignored and fetched from the CesiumC release at CD time.publish-onlyskips the fetch. The gate caught it andpublishwas skipped, which is the gate working, but it is a trap worth removing in the toolbox rather than here.