ci: Build iOS harness with generic simulator - #1062
Merged
Merged
Conversation
mrousavy
force-pushed
the
chore/fix-ios-harness-build-destination
branch
from
May 27, 2026 22:42
65f0d90 to
347e756
Compare
mrousavy
force-pushed
the
chore/fix-ios-harness-build-destination
branch
from
May 28, 2026 08:36
347e756 to
c0caccf
Compare
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
1 participant
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.
Summary
Reason
Recent macOS images do not always expose the configured simulator as an available Xcode build destination before
futureware-tech/simulator-actioncreates it. The app build does not need a named simulator, so this keeps the build independent of the E2E target device.Validation
ruby -e 'require "yaml"; YAML.load_file(".github/workflows/harness-ios.yml"); puts "ok .github/workflows/harness-ios.yml"'