›_ Codex Issues
Codex Issues / #30750

Codex mobile pairing fails on iPad Pro running 27 beta 2; QR and manual code both fail

Open 💬 8 comments Opened Jun 30, 2026 by kvarnelis

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

Version 26.623.70822

What subscription do you have?

Max x 20

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

Title:
Codex mobile pairing fails on iPad Pro running 27 beta 2; QR and manual code both fail

Summary:
An iPad Pro running 27 beta 2 cannot pair with Codex remote control from ChatGPT/Codex. The ChatGPT app shows:
“Pairing failed. Something went wrong while pairing. Try scanning the code again.”

Both QR scanning and manual pairing code fail.

What I tried:

  • Confirmed same ChatGPT account/workspace
  • No ChatGPT app update available
  • Force quit/retry
  • Sign out/in
  • Reinstall ChatGPT app
  • Manual code entry
  • Another iPad (running 26.5) can pair successfully to the same Mac/host/account
  • I tried doing this on another Mac running Codex, and the same problem happened

Host details:

  • Codex Desktop: 26.623.70822
  • Host OS: 26.4.1
  • Pairing attempt observed at: 2026-06-30 14:07:31 EDT
  • Host log request id: 020bec6c-6ba1-4df0-af45-7e20088d593a
  • Host appears to start pairing successfully; no visible host-side HTTP error in local logs.
  • Later log line: remote control connection closed at about 14:08:23 EDT

Expected:
The iPad should pair and appear as a remote Codex device.

Actual:
The iPad shows the “Pairing failed” modal every time.

Attachment:
Screenshot of the pairing failed modal.

What steps can reproduce the bug?

Feedback ID: 019f1549-b1a1-7273-9c1f-b84f4a6c947d

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

8 Comments

ibuki2003 · 1 month ago

I'm seeing a similar problem on Android 17 QPR preview build, while the same flow works on Android 16.

This may only be loosely related since it's a different platform/device.
If it would be better to track this separately, I'm happy to open a new issue with the device/app/OS details.

raz123 · 1 month ago

Same issue on Android 13 mobile and MacOS laptop (using latest ChatGPT Codex Desktop app).

kvarnelis · 1 month ago

Additional device-side evidence captured from the affected iPad over USB on 2026-07-13.

Affected device:

  • iPad Pro 11-inch (M4), iPad16,4
  • iPadOS 27.0 beta build 24A5380h
  • Developer Mode enabled
  • ChatGPT bundle com.openai.chat

Reproduction timestamp: approximately 2026-07-13 00:21:12 EDT.

The iPad unified log shows that ChatGPT:

  1. Reaches the service successfully over Wi-Fi; TLS trust evaluation and certificate verification succeed.
  2. Receives the pairing/challenge requests with HTTP 200 responses.
  3. Calls SecKeyCreateWithData and SecKeyVerifySignature, indicating that the pairing challenge signature is parsed and verified.
  4. Calls SecKeyCreateRandomKey; CryptoTokenKit reports SEPClientObject: createKey.
  5. Adds the generated key with SecItemAdd_ios, reads the Secure Enclave key, and exports the public key.
  6. Immediately calls SecItemDelete_ios for that newly created key, after which the UI reports pairing failure.

The same sequence reproduced twice. All visible network transactions in the failure window completed successfully at the transport/HTTP layer. The Codex host on the Mac recorded no corresponding enrollment completion or rejection at the same timestamp. This places the failure after challenge retrieval/verification but before the mobile client becomes an enrolled remote-control client.

The immediate Secure Enclave/Keychain rollback may be the most useful point to trace. An HTTP 200 could still contain an application-level rejection in its response body; production unified logging redacts that body.

Raw device archives were retained locally and are not attached because they contain unrelated private device activity. I can provide a narrowly scoped diagnostic artifact or additional request identifiers if an OpenAI maintainer specifies what is needed.

taoyuanyuan · 1 month ago

The same issue on Android 1.2026.288 and MacOS Codex 26.707.62119.

xxxsen · 1 month ago

I had the same issue on Android and Windows. It appears to be related to a security restriction. My phone was rooted, and I kept getting the error: “Something went wrong while pairing. Try scanning the code again.”

After switching to a non-rooted phone, the pairing worked successfully.

ogisa-setsuna · 1 month ago

Same issue on HarmonyOS 4.2.0.191 with microG service and Windows ChatGPT 26.715.72359.

taoyuanyuan · 1 month ago
Same issue on HarmonyOS 4.2.0.191 with microG service and Windows ChatGPT 26.715.72359.

@ogisa-setsuna After upgrading from HarmonyOS 4.2 to HarmonyOS 6.1, Codex Remote Control pairing succeeded.

9:07

ogisa-setsuna · 1 month ago

@taoyuanyuan Well thank you but i don't want to use Harmony 6 yet.