Fleet changelogs · dev.ecs0.net
rdmsm4x-changelog-20260927-0000-xcode-repair-and-dev-update-2-17

rdmsm4x — Xcode repair, stale Xcode retirement, dev_update 2.17 fleet-wide

Summary: Xcode on rdmsm4x is back on 27.0 (27A266a), launches, has release simulator runtimes, and is signed in to team ZU2882L4HT; ~14 GB of stale Xcode copies are in the Trash; dev_update 2.17 (payload 2.25) now reports the Xcode faults it missed and is canonical on all six Macs.

What was wrong

  1. Xcode would not open. At 23:47 the RTTy lane (TASK-20260926-72, build 526 construct) sudo-swapped Xcode 26.6 into /Applications/Xcode.app. macOS 27 refuses 26.x (LaunchServices -10664). The lane's restore trap put 27.0 back at 23:51. The lane's own restore_xcode27.zsh calls this swap LEGACY, so I routed the fix to the RTTy lane on the bus rather than editing their scripts.
  2. No matching simulator runtimes. Xcode 27.0 release (iOS SDK 24A430) sat beside 7 beta runtimes (44.3 GB). None matched, so Xcode asks for a platform download on every launch.
  3. Stale Xcodes outside the retire lifecycle: ~/Archive/offhost-jdmbair13m5-20260923/ (27.0 beta 6, plus a 27.0 copy mislabelled Xcode-17F112.app), two 27.0 beta 5 bundles in ~/Library/Developer/Xcode-archive, and a beta 6 .xip in ~/Archive/xcode-staging-20260831.
  4. dev_update said all green. Its Xcode section never looked at simulator runtimes, at /Applications/Xcode.app being unopenable, at same-build duplicates, or at ~/Archive/offhost-*. Its info/warn/err/note lines also never reached ~/scripts/dev_update_<ts>.log, so Rich's 23:38 log had empty Xcode sections.

Changes on rdmsm4x

dev_update 2.17 (payload 2.25), fleet-wide

Verification

Undo

Routed, not done here

Documentation (added 2026-09-27 00:22 EDT)

Post-check at wrap-up (2026-09-27 17:28 EDT)