ci: resolve iOS simulator at runtime instead of pinning iPhone 16#54
Merged
Conversation
The `build-and-test` job hardcoded `-destination 'platform=iOS Simulator, name=iPhone 16'`. When the `macos-latest` runner image rolls forward, that model is no longer preinstalled (current image ships iPhone 16e / 17 / 17 Pro / Air, etc.), so xcodebuild fails destination resolution with exit 70 before running a single test. Resolve an available iPhone simulator at runtime via `simctl` + `jq` and pass it by `id`. A generic destination (`generic/platform=iOS Simulator`) is not an option here because the job runs `test`, which requires a bootable device. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J9mruKG6RSYg6SfPaq6MPG
alexvbush
added a commit
to haeseoklee/RIBs-iOS
that referenced
this pull request
Jul 12, 2026
Pulls in the CI simulator-destination fix (uber#54) so this PR's build-and-test job can resolve a simulator on the current runner image and run the suite.
This was referenced Jul 12, 2026
Merged
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.
Problem
The
build-and-testjob hardcodes the test destination:-destination 'platform=iOS Simulator,name=iPhone 16'When the
macos-latestrunner image rolls forward,iPhone 16is no longer preinstalled (the current image ships iPhone 16e / 17 / 17 Pro / Air, etc.). xcodebuild then fails destination resolution with exit 70 — "Unable to find a device matching the provided destination specifier", before compiling or running a single test. This is currently red on open PRs (e.g. #51) through no fault of the change under review.Fix
Resolve an available iPhone simulator at runtime with
simctl+jqand pass it byid:This picks whatever iPhone simulator the runner actually has, so it won't rot on model-name churn.
A generic destination (
generic/platform=iOS Simulator) is not an option here: the job runstest, which requires a bootable device — generic destinations only build.Notes
jqis preinstalled on GitHub-hosted macOS runners.xcodebuild testwith-destination "platform=iOS Simulator,id=<udid>"runs the suite green.🤖 Generated with Claude Code