›_ Codex Issues
Codex Issues / #37019

Codex Desktop auto-update breaks macOS Monterey support (build 6223 requires macOS 13)

Resolved 💬 4 comments Opened Aug 5, 2026 by liuchuang Closed Aug 6, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

Build: 6223 Version: 26.730.61309

What subscription do you have?

/Applications/ChatGPT.app/Contents/MacOS/ChatGPT

What platform is your computer?

_No response_

What issue are you seeing?

Before update:
Build: 6119
macOS: 12.7.6
Architecture: x86_64
Works normally

After Sparkle update:
Build: 6223
Version: 26.730.61309

Launch error:
NSOSStatusErrorDomain Code=-10825

Mach-O:
LC_BUILD_VERSION minos 13.0

What steps can reproduce the bug?

Before update:
Build: 6119
macOS: 12.7.6
Architecture: x86_64
Works normally

After Sparkle update:
Build: 6223
Version: 26.730.61309

Launch error:
NSOSStatusErrorDomain Code=-10825

Mach-O:
LC_BUILD_VERSION minos 13.0

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 23 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #37002

Powered by Codex Action

0x2a94b5 · 22 days ago

Confirmed on another Intel Mac running macOS Monterey 12.7.6.

Working version:

  • 26.727.51351, build 6119

Broken update:

  • 26.730.61639, build 6234

The Sparkle appcast advertises minimumSystemVersion 12.0, so the update is offered and installed on macOS 12, but the updated application cannot launch because its executable requires macOS 13.

After recovery, the installed application reverted to build 6119. Crash dumps also show bundled native helpers failing on macOS 12 due to missing Foundation/Swift symbols.

This confirms that the issue reported here also affects the latest 26.730 build.

Related: #37070 and #28678

gpeal contributor · 22 days ago

Sorry, Chrome no longer supports macOS 12 and in order to pick up the latest security updates, we had to bump the minimum supported macOS version.
https://chromestatus.com/feature/5077742779498496

If you get stuck, you can download the last working version here:
Apple Silicon
Intel

FatNine · 16 days ago

Adding another data point as an affected user, because I don't think the core problem has actually been addressed by the "Chrome dropped macOS 12" rationale.

My setup: MacBook Pro A1707 (2017, Intel), macOS 12.7.6 Monterey — this is the hardware ceiling for this machine, it cannot be upgraded to macOS 13. Was running Codex build 6119 fine; Sparkle auto-updated to build 6223+ → app no longer launches (NSOSStatusErrorDomain Code=-10825, LC_BUILD_VERSION minos 13.0).

The actual bug isn't "you dropped macOS 12" — it's that the update channel still advertises macOS 12 as supported. The Sparkle appcast declares minimumSystemVersion 12.0, so macOS 12 users are offered and silently installed an update whose Mach-O requires minos 13.0. That's an inconsistent contract between the update manifest and the shipped binary, and it's what turns a policy change into a bricked install with no opt-out.

Two fixable defects:

  1. The appcast's minimumSystemVersion should be 13.0, not 12.0. Then macOS 12 clients stop pulling builds they can't run. One-line fix; the difference between graceful sunset and silent breakage.
  2. There's no way to pin a version or disable auto-update. The downgrade link helps once, but the moment Sparkle runs again it re-installs the broken build. Affected users are in a loop unless they block oaistatic.com at the network level.

Thanks for the downgrade link — it unblocks me for now — but without one of the two fixes above, every Mac that can't go past Monterey is one reboot away from being broken again.