Conversation
hggzm
force-pushed
the
users/hggzm/fix/ios-ci-simulator-runtime
branch
3 times, most recently
from
1054be0 to
555b934
Compare
…silience The Xcode@5 ADO task internally resolves simulator destinations and fails (exit 70) when no matching simulator is found, even with destinationPlatformOption: default. This has been a recurring issue as macos-latest runner images get updated. Fix: Replace Xcode@5 with direct xcodebuild script steps that: - Dynamically discover available simulators via xcrun simctl - Fall back to generic/platform=iOS Simulator if none found - Match the approach used in the working GitHub Actions CI Applied to both ios-ci-template.yml and ios-build-template.yml.
hggzm
force-pushed
the
users/hggzm/fix/ios-ci-simulator-runtime
branch
from
555b934 to
ff8ed54
Compare
GabrielMedAlv
approved these changes
Mar 17, 2026
VikrantSingh01
approved these changes
Mar 18, 2026
hggzm
added a commit
that referenced
this pull request
Mar 18, 2026
The Gradle@3 ADO task runs gradlew build which includes assembleRelease. The release packaging step (PackageAndroidArtifact IncrementalSplitterRunnable) fails intermittently on shared macOS runners due to file locking race conditions. Fix: Replace Gradle@3 with a direct script step that runs only assembleDebug + testDebugUnitTest. This is sufficient for PR validation (we only need to verify the code compiles and tests pass) and avoids the flaky release packaging entirely. Matches the approach used for the iOS CI fix (PR #600).
This was referenced Mar 18, 2026
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
3 participants
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.
The
macos-latestAzure DevOps runner image was updated (Xcode 16.4) and no longer hasiPhone 16simulator pre-installed, causing the iOS PR CI to fail with:This has been a recurring issue — previously the simulator was changed from
iPhone 15 ProtoiPhone 16(commit bdd3e20).Fix
Instead of hardcoding a device name that breaks every time the runner image updates, this PR adds a small discovery step that dynamically finds the first available iPhone simulator using
xcrun simctl list devices availableand passes it as a pipeline variable.Changes:
Discover available iOS Simulatorscript step, remove hardcodedsdk: iphonesimulator18.5(useiphonesimulator), usedestinationPlatformOption: customwith discovered simulator nameiPhone 12)This permanently fixes the recurring "simulator not found" CI failures without requiring manual updates when Apple/Azure updates macOS runner images.