macOS: Codex 26.609.71450 installs successfully but app bundle fails codesign verification
Summary
Codex Desktop updated successfully to 26.609.71450 / build 3965, but the installed macOS app bundle still fails code signature verification.
This is related to #28373, but appears to be a post-update signature verification issue rather than only an updater failure. I previously commented there when the installed version was 26.609.41114 / build 3888; after the later update to 26.609.71450 / build 3965, the bundle still fails verification.
Environment
macOS: 26.5.1 (25F80)
Architecture: arm64
Codex.app: 26.609.71450
Bundle version: 3965
Bundle ID: com.openai.codex
Install path: /Applications/Codex.appFrom /Applications/Codex.app/Contents/Info.plist:
CFBundleShortVersionString = 26.609.71450
CFBundleVersion = 3965
ChromiumBaseVersion = 149.0.7827.54
TeamIdentifier observed via codesign = 2DC432GLL2What happened
Initially the updater reported that the update was signed incorrectly. After retrying/restarting, Codex updated and now reports the newer installed version.
However, the installed app bundle still fails macOS code signature verification.
Reproduction / diagnostics
Run:
codesign --verify --deep --strict --verbose=4 /Applications/Codex.appObserved output:
/Applications/Codex.app: invalid signature (code or signature have been modified)
In architecture: arm64Run:
spctl --assess --type execute -vv /Applications/Codex.appObserved output:
/Applications/Codex.app: internal error in Code Signing subsystemRun:
codesign -dv --verbose=4 /Applications/Codex.appRelevant output:
Executable=/Applications/Codex.app/Contents/MacOS/Codex
Identifier=com.openai.codex
Format=app bundle with Mach-O thin (arm64)
CodeDirectory v=20500 size=764 flags=0x10000(runtime) hashes=13+7 location=embedded
CandidateCDHash sha256=9321e615e42dc089e7e977e71ec97cd05424dbc5
CandidateCDHashFull sha256=9321e615e42dc089e7e977e71ec97cd05424dbc5b2aa154e4f7283c0e150706e
CMSDigest=9321e615e42dc089e7e977e71ec97cd05424dbc5b2aa154e4f7283c0e150706e
Signature size=9048
Authority=(unavailable)
Notarization Ticket=stapled
Info.plist=not bound
TeamIdentifier=2DC432GLL2
Runtime Version=26.2.0
Sealed Resources version=2 rules=13 files=7929Expected behavior
After a successful update, /Applications/Codex.app should pass macOS code signature verification and Gatekeeper assessment.
Actual behavior
The app appears updated, but the app bundle remains invalid according to codesign --verify --deep --strict, and spctl cannot assess it successfully.
Why this seems separate from #28373
#28373 tracks the updater failing with a signed-incorrectly style error. In this case, the updater now appears to complete, but the resulting app bundle is still not code-signature-valid.
Notes
I searched for open issues with the same top-level /Applications/Codex.app post-update signature failure. I found related signing/helper issues, but not an identical open issue for the main installed app bundle on 26.609.71450 / build 3965.
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Thanks. I reviewed the suggested duplicates.
I do not think #27559 is a duplicate: that issue is mainly about Desktop slowness/recovery after restart, while this issue is specifically about the top-level
/Applications/Codex.appbundle failingcodesign --verify --deep --strictafter a successful update.#28069 looks related, especially around Sparkle/macOS signing/provenance after auto-update, but it seems distinct: #28069 reports an AMFI library-load denial for
better_sqlite3.nodeon macOS 27, while this issue is about the top-level app bundle itself failing signature verification:/Applications/Codex.app: invalid signature (code or signature have been modified)
In architecture: arm64
So I’m keeping this open as a separate post-update top-level app bundle signature failure, while linking #28069 as likely related.
Update after installing the newer build:
Codex.app: 26.611.61753
Bundle version: 4008
ChromiumBaseVersion: 149.0.7827.115
macOS: 26.5.1 (25F80)
Architecture: arm64
The app did update from 26.609.71450 / build 3965 to 26.611.61753 / build 4008, but the top-level bundle still fails signature verification:
/Applications/Codex.app: invalid signature (code or signature have been modified)
In architecture: arm64
spctl also still fails:
/Applications/Codex.app: internal error in Code Signing subsystem
Updated codesign -dv --verbose=4 details include:
CandidateCDHash sha256=d0897f7c3886f774b00c03942f7726bdda03de6c
CDHash=d0897f7c3886f774b00c03942f7726bdda03de6c
TeamIdentifier=2DC432GLL2
Authority=(unavailable)
Notarization Ticket=stapled
Info.plist=not bound
Runtime Version=26.0.0
Sealed Resources version=2 rules=13 files=7898
This now also looks closely related to #28583, which reports the same top-level /Applications/Codex.app signature verification failure plus syspolicyd/trustd high CPU impact.
So the update changed the installed version and signing metadata, but did not resolve the top-level app bundle signature verification failure.
Update after installing another newer build:
Codex.app: 26.611.62324
Bundle version: 4028
ChromiumBaseVersion: 149.0.7827.115
macOS: 26.5.1 (25F80)
Architecture: arm64
The app updated from 26.611.61753 / build 4008 to 26.611.62324 / build 4028. The signing metadata changed again:
CandidateCDHash sha256=0e2ee7405d83d5701b409a3a17a94d589937d324
CDHash=0e2ee7405d83d5701b409a3a17a94d589937d324
TeamIdentifier=2DC432GLL2
Authority=(unavailable)
Notarization Ticket=stapled
Info.plist=not bound
Runtime Version=26.0.0
Sealed Resources version=2 rules=13 files=7898
However, the top-level bundle still fails signature verification:
/Applications/Codex.app: invalid signature (code or signature have been modified)
In architecture: arm64
spctl also still fails:
/Applications/Codex.app: internal error in Code Signing subsystem
So this newer update changed the installed build and codesign hashes, but still did not resolve the top-level app bundle signature verification failure.
Update after installing the latest Codex Desktop release:
26.616.307094108arm645ebcbc238499b4331e5d21d5414e2687ee600462The original failures still reproduce:
$ codesign --verify --deep --strict --verbose=4 /Applications/Codex.app
/Applications/Codex.app: invalid signature (code or signature have been modified)
In architecture: arm64
$ spctl --assess --type execute -vv /Applications/Codex.app
/Applications/Codex.app: internal error in Code Signing subsystem
Current signature metadata still reports:
Authority=(unavailable)Notarization Ticket=stapledInfo.plist=not boundTeamIdentifier=2DC432GLL2Sealed Resources version=2 rules=13 files=8047So the update changed the build, resource set, and signing hash, but did not resolve the top-level app bundle verification failure.
Another Codex Desktop update was installed and tested:
26.616.321564157arm64f577dfe786d8e67ae1e9854e765f30bac8ae3f37The same verification failures still reproduce:
$ codesign --verify --deep --strict --verbose=4 /Applications/Codex.app
/Applications/Codex.app: invalid signature (code or signature have been modified)
In architecture: arm64
$ spctl --assess --type execute -vv /Applications/Codex.app
/Applications/Codex.app: internal error in Code Signing subsystem
The current metadata still reports:
Authority=(unavailable)Notarization Ticket=stapledInfo.plist=not boundTeamIdentifier=2DC432GLL2Sealed Resources version=2 rules=13 files=8047The update changed the version, build, and signing hash, but the app bundle still fails code-signing verification.