macOS 26.5: New Chat fails with "DeviceCheck token generation is unavailable" after updating to ChatGPT 26.707.72221

Resolved 💬 1 comment Opened Jul 16, 2026 by mervinweber Closed Jul 16, 2026

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

Version 26.707.72221

What subscription do you have?

20 Dollar Plan

What platform is your computer?

ProductName: macOS ProductVersion: 26.5 BuildVersion: 25F71

What issue are you seeing?

FeedbackID 019f3cb8-d5f5-7461-afa2-ad826eaecc39

Summary

After updating the ChatGPT macOS desktop app via the built-in updater to version 26.707.72221, starting a normal Chat fails with:

DeviceCheck token generation is unavailable

Existing Projects continue to work normally, and ChatGPT works normally in the browser.

Environment

  • ChatGPT Desktop: 26.707.72221
  • Release date: Jul 14, 2026
  • macOS: 26.5 (25F71)
  • Hardware: Apple M3 MacBook Air

Reproduction

  1. Update ChatGPT using the built-in updater.
  2. Launch the application.
  3. Attempt to start a normal Chat.

Expected

A new chat opens normally.

Actual

The app reports:

DeviceCheck token generation is unavailable

Projects continue to function normally.

The browser version (chatgpt.com) also works normally.

Relevant log output

Repeated failures attempting to connect to Apple's DeviceCheck daemon:

failed to do a bootstrap look-up:
xpc_error=[3: No such process]

Failed to connect to daemon.

Failed to check if client is supported.

The app repeatedly attempts to connect to:

com.apple.devicecheckd

Verification

Running:

launchctl print system/com.apple.devicecheckd

returns:

Could not find service "com.apple.devicecheckd" in domain for system

Likewise:

launchctl print gui/$(id -u)/com.apple.devicecheckd

returns:

Could not find service "com.apple.devicecheckd"

Additional Notes

  • Browser works normally.
  • Existing Projects work normally.
  • Only the New Chat flow fails.
  • The issue began immediately after updating via the built-in updater.

What steps can reproduce the bug?

Feedback ID: 019f3cb8-d5f5-7461-afa2-ad826eaecc39

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗