Repository navigation
Description
Problem
All iOS build jobs in Expensify/App select Xcode by pinning the DEVELOPER_DIR environment variable to /Applications/Xcode_26.2.app/Contents/Developer. That pin was set in Update Xcode version to 26.2 in Rock iOS build workflows back in January 2026, when the runner images made 26.2 the default and the iOS 26.0 simulator stopped being available under Xcode 26.0.1.
Since then all macOS jobs moved to Blacksmith macos-latest runners. Those track the macOS 26 image and mirror the GitHub-hosted macOS 26 runner image, which currently ships:
| Xcode | Notes |
|---|---|
| 26.6 | newest (build 17F113) |
| 26.5 | image default |
| 26.4.1 | |
| 26.3 | |
| 26.2 | what App pins today |
| 26.1.1 | |
| 26.0.1 |
So the iOS builds run three releases behind the image default. Two consequences:
- Builds compile against an older toolchain and older simulator runtimes than the runner otherwise provides.
- The four macOS jobs that don't set
DEVELOPER_DIR(verifyPodfile.yml,createNewVersion.yml,syncVersions.yml,verifyParserFiles.yml) silently use the image default, so they're already on a different Xcode than the build jobs.
This drift is what caused the previous breakage: builds failed with iOS 26.0 is not installed. Please download and install the platform from Xcode > Settings > Components., and the failures were initially masked by S3 remote-cache hits that completed in ~5 seconds.
Solution
Bump all five pins to /Applications/Xcode_26.6.app/Contents/Developer:
| File | Line | Job(s) |
|---|---|---|
.github/workflows/buildIOS.yml |
53 | build — the reusable iOS build, called from deploy.yml, verifyHybridApp.yml, buildAdHoc.yml |
.github/workflows/deploy.yml |
445 | iosUploadTestflight (Fastlane) |
.github/workflows/deploy.yml |
526 | iosSubmit (Fastlane) |
.github/workflows/remote-build-ios.yml |
50 | build (Rock remote build matrix) |
.github/workflows/publishReactNativeiOSArtifacts.yml |
29 | workflow-level env, covers Build iOS Slice and Compose XCFramework |
All five must change in one commit. The previous two bumps each needed a follow-up commit because deploy.yml was missed, and that broke the staging deploy.
Follow-ups (not in this issue)
Mobile-Expensify/.github/workflows/lint-swift.yml:19still pinsXcode_16.2.0.appon GitHub-hostedmacos-15-xlarge. It lives in the submodule, so it needs a separate PR againstExpensify/Mobile-Expensify.- There is no single source of truth for the Xcode version — no
.xcode-versionfile, nosetup-xcodeaction, no composite action, andworkflow_calldoes not inheritenvfrom the caller. AgetXcodeVersioncomposite action alongside the existinggetJavaVersionone would stop this from drifting again. ios/Podfile:39,109still calls__apply_Xcode_14_3_RC_post_install_workaround, which is almost certainly dead under Xcode 26.
Activity
melvin-bot commentedon Aug 1, 2026
@mountiny
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.47-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-08-08. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
[-][Internal] Update iOS build workflows to Xcode 26.6[/-][+][Due for payment 2026-08-08] [Internal] Update iOS build workflows to Xcode 26.6[/+]12 remaining items
mountiny commentedon Aug 6, 2026
almost there
[-][Due for payment 2026-08-11] [Internal] Update iOS build workflows to Xcode 26.6[/-][+][Due for payment 2026-08-21] [Internal] Update iOS build workflows to Xcode 26.6[/+]melvin-bot commentedon Aug 14, 2026
@mountiny @war-in
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.53-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-08-21. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
melvin-bot commentedon Aug 17, 2026
@war-in Whoops! This issue is 2 days overdue. Let's get this updated quick!